GitVersion: bump semver on merge through dev → qa → uat → main #4598
Unanswered
carlosantiagorojas
asked this question in
Q&A
Replies: 0 comments
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.
-
I’m using GitVersion v6.0.5 in Azure DevOps
Hello, I want to know if a configuration exist so that it can bump the semver in a pre-release branch. I have 4 branches, dev, qa uat and main.
And i want that each branch bump the semver version when a feature/bugifx/hotfix branch is merged and it carries the calculated semver when merging between this branches.
feature/… → dev
dev → qa
qa → uat
uat → main (production)
I’d like each merge to:
What I Expect:
feature → dev
→ 1.3.0-dev
dev → qa
→ 1.3.0-qa
qa → uat
→ 1.3.0-uat
uat → main
→ 1.3.0 (no prerelease)
And if I merge a hotfix/bugfix into any of those branches with +semver:patch, it should bump only the patch portion:
e.g. merging a +semver:patch into qa at 1.3.0-qa → 1.3.1-qa
What I’ve Tried
None of these have produced the desired bump on merge; dev stays at 1.2.6-dev, qa never bumps, etc.
Question
Any pointers to a working sample config or documentation section would be hugely appreciated. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions