gitflow-maven-plugin icon indicating copy to clipboard operation
gitflow-maven-plugin copied to clipboard

Published 20 hours ago • verified publisher icon aleksandr-m

Why is commitDevelopmentVersionAtStart only allowed if there are separate development and production branches?

Open beatngu13 opened this issue 4 years ago • 2 comments

First of all: Thank you for this awesome plugin, super helpful (especially for automation)! 🙏

I wonder why commitDevelopmentVersionAtStart is only allowed if there are separate development and production branches? If, for instance, one uses a GitHub Flow-like workflow, i.e. master for development but with dedicated release branches. Wouldn't it make sense to allow to update the version on master when a release branch is started?

beatngu13 avatar Aug 18 '20 12:08 beatngu13

@beatngu13 See https://github.com/aleksandr-m/gitflow-maven-plugin/pull/61#issuecomment-318189739

aleksandr-m avatar Aug 18 '20 21:08 aleksandr-m

Hey @raehalme,

@aleksandr-m pointed me to your comment:

I cannot see how it would make sense to enable the setting when using the single branch model.

What's your say on the workflow I've described above? I believe it's not that uncommon, also GitHub is suggesting separate release branches on top of GitHub Flow in special situations:

https://lab.github.com/githubtraining/create-a-release-based-workflow

beatngu13 avatar Aug 21 '20 11:08 beatngu13