Asbjørn Ulsberg

> Unfortunately tagging develop with `1.0.0` does not give me behavior I want. This will cause versions on `develop` have a `1.0.0` version (without the `-alpha`). That only happens if...

Did #3190 resolve this?

Thank you for reporting this. It is a known issue, but we just haven't gotten around to debug it yet. I have started in #2743, but I have not been...

@arturcic, so the `Version` argument was never passed to the compiler. That explains it! :)

I'm not sure the precedence `*-version-bump-message` takes over `no-bump-message` is conscious or accidental. Either way, I think it can be argued as strongly for either taking precedence over the other....

As I'm not a user of `commit-message-incrementing` myself, please answer me this: Would you enforce a `no-bump-message` or `*-version-bump-message` in every commit across all branches? Can you please explain your...

Have you read the [section on conventional commits in the documentation](https://gitversion.net/docs/reference/version-increments#conventional-commit-messages)?

Right. Thanks for providing the examples, that clears things up. When combining conventional commits with `no-bump-message`, I can definitely see how reversing the precedence of `*-version-bump-message` and `no-bump-message` makes sense....

> Merge pull request https://github.com/GitTools/GitVersion/issues/1 from bananaCorp/develop To me, this looks like a merge from a remote into a local `develop` branch, instead of what it imho should have been:...

If you are closer to a Git Flow development model with `develop`, `feature`, `release` branches, and so on, using the default mode `ContinuousDeployment` or `ContinuousDelivery` would be better.