Hello I am testing GitVersion and I added a Commit Message +semver:minor and now the minor number of the version is increased. If I do it by mistake and what to rollback what is recommended?
-> I tried with a Revert and it didn't work because the version is based on the commit messages, but I am wondering if we have lot of commits after the Commit Message with the SemVer increase and later we want to fix it. Maybe changing the base GitVersion.yml is the easiest way.
-> I achieve what I want using Cherry-Pick, selecting the commits and placing in another branch, then deleting the branch with the wrong commit messages. I am looking for something that could be easier than that.
Within the GitVersion configuration file, you can add a list of the commits (i.e. the SHA's) that you want GitVersion to ignore as part of establishing the correct semantic version number.
This takes the following format:
ignore:
sha:
- 2a4757b270f7946122ba6622e3d2e72b2b2808a7
- 3e91c23637b97bc4e4c3234f93ffd03e6af70e8c
You can see a full example of this in use here
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With