search

aleksandr-m / gitflow-maven-plugin

The Git-Flow Maven Plugin supports various Git workflows, including GitFlow and GitHub Flow. This plugin runs Git and Maven commands from the command line.
https://aleksandr-m.github.io/gitflow-maven-plugin/
Apache License 2.0
493 stars 181 forks source link

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

Open beatngu13 opened 4 years ago

beatngu13 commented 4 years ago

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?

aleksandr-m commented 4 years ago

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

beatngu13 commented 4 years ago

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