Reputation: 4810
Does the git-flow
workflow intend for one feature per release, so that as soon as a feature is merged into develop
, a corresponding release branch is made? Or can a release branch contain multiple features (each of which were merged into develop
that subsequently became a single release branch)?
I understand what's possible with git-flow. I'm asking what was the intention of git-flow regarding features and releases...what is the best practice, not all that is possible.
Upvotes: 1
Views: 188
Reputation: 61
First of all, GitFlow permits you do so much features as you want.
Now, it's your decision how you'll work with it.
Some developers develop one feature and when finish this feature creates a release.
Some developers develop many features and times in times (eg each two weeks) they creates a new release with all features that they have in the develop branch.
Upvotes: 2
Reputation: 995
Gitflow can contain multiple features per release as long as you are following the proper merging strategy, which it sounds like you are.
Upvotes: 1