Replies: 1 comment 1 reply
-
|
Effectively, this question could be simplified to, how to tell Gitversion to ignore all tags on commits in a release branch, and strictly use the release branch name/version to compute the next tag/version. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
I'm having an issue trying to achieve a desired outcome and I'm hoping someone knows which setting(s) need to be changed.
Objective:
When merging a commit into a
releasebranch, the version generated for the release branch should never increment.Example:
If I have:
mainthat is tagged0.2.0-alpha.1release/0.1.0If I merge
mainintorelease/0.1.0, it will currently make the release branch's tag to0.2.0-1(this is because it adds the commit to the release branch with the0.2.0-alpha.1tag). I don't want this, instead, I want the tag to match the release branch name, and be0.1.0-1, even if there is a tag in the release branch that is greater than the release branch.Information
I'm using, 6.0.0-rc.1, the default
workflow: GitFlow/v1, with the following configuration modifications:What I've been unable to determine is what configuration changes need to be made to the
releasebranch configuration to achieve what I'm looking for.Beta Was this translation helpful? Give feedback.
All reactions