GitVersion: Reverting tags to a lower version scheme does not seem to work
We’ve recently decided to change our internal version numbering for a large (50K commits) repo from a year-based number to a more traditional version number. As such, we’ve replaced all our existing tags numbered like 2015.x.y
to 7.x.y
. Unfortunately, GitVersion 3.6.1 still tries to extract information from the merge commits that happened somewhere in the history of the repo. For example, it decides the base-version to be 2015.5.1
using this commit message:
Base version used: Merge message 'Merge branch 'Development/2015.05.01' into 576446_Client_Reports': 2015.5.1 with commit count source 4ec2b7c3c6270b3ebd14e7ccf7dbfd84512bf945
We’ve tried to tweak the global commit-message-incrementing
setting or the branch-specific prevent-increment-of-merged-branch-version
and track-merge-target
, but neither is doing the trick. Is this a bug or am I doing something wrong?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 18 (11 by maintainers)
Good idea, lets do that for v4. Anyone want to put together an up for grabs issue.
Maybe something like
Other ideas?
Ah, that helps. I treated it as a top-level global setting.
I think that would be very useful. I think we should be able to enable/disable all the strategy’s.