-
I think we should organize our releases a bit better, although we haven't had any trouble in this area, yet. What I could think of is the following:
- Branch `release` that collects planned features f…
-
I had to chance to talk to @jeremydmiller in RL. I'm honored. Here is the summary of the idea I gave him during a tube ride:
It would be extremely helpful if ripple could detect based on the GitFlow …
-
As stated in #56 it might be a good idea to tag the version on commits. I wanted to check the diff between two versions, but can't do so without checking each commit individually to find the versions …
-
In the language-agnostic test suite, there are several test strings where the options take the form
```
Options: --option-name
```
[One example can be found here](https://github.com/docopt/docopt/bl…
-
We de-facto use the gitflow branching model at https://nvie.com/posts/a-successful-git-branching-model/
BUT the "master/develop" branches are making double duty and serve not purpose.
In practice al…
-
I suggest to start developing according to Vincent Driessen (It's not that complicated). I also suggest altering the model to push feature branches to origin as well for review purposes.
Here you may…
M4a1x updated
10 years ago
-
Quote from original report by @kretes at nvie/gitflow#358
> When using branching model it may happen that release is created, some commits are applied to it, but then it is abandoned - i.e. not deplo…
-
When you see this project and don't know the maintainers personally, it is hard to know where to start.
Other projects have contributing guidelines for this. A nice guide how to add them is here: h…
-
https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
-
[The original model](http://nvie.com/posts/a-successful-git-branching-model/) is a bit too complicated for the first milestone, but it would be nice to have something that could be eventually expanded…