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

[beatngu13]

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]

@beatngu13 See #61 (comment)

[beatngu13]

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