You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be the same as #2590 but reverting to 5.6.4 doesn't fix the issue for me. 5.5.1 seems to work though. If it is the same issue feel free to close this as a duplicate.
Describe the bug
master branch is tagged with 2.1.7 at the latest commit. If I run GitVersion against it I get the correct 2.1.7 version. I correctly identifies the tag. But if I move to the develop branch it gives me 0.1.0. The only difference between the two branches is we've merged develop -> master. We release from master so it is always our base branch. Feature and bugfix work happens from branches off of develop.
Expected Behavior
I would expect that develop should be versioning at 2.2.0 or 2.1.8 depending on the config.
Actual Behavior
I get a version of 0.1.0 for develop and any feature or bugfix branches.
Steps to Reproduce
I've got no clue. I tried to create a sample repo that reproduced it but have been unsuccessful. It's something about this repository but I'm not sure what.
Your Environment
Version Used: 5.5.1, 5.6.4, 5.6.11
Operating System and version: Ubuntu 20.04, Windows 10
Link to your project: Private repository unfortunately
I've tried it with and without a GitVersion.yml file. It doesn't seem to matter it never picks up the master branch tags in anything but when on the master branch.
Ignore my comment above it not working with 6.5.4. I must have screwed up that test because I just retested it and it works with 5.6.4 and fails with 5.6.5. I'm going to close this since it looks the same as the other bug.
This may be the same as #2590 but reverting to 5.6.4 doesn't fix the issue for me. 5.5.1 seems to work though. If it is the same issue feel free to close this as a duplicate.
Describe the bug
master branch is tagged with 2.1.7 at the latest commit. If I run GitVersion against it I get the correct 2.1.7 version. I correctly identifies the tag. But if I move to the develop branch it gives me 0.1.0. The only difference between the two branches is we've merged develop -> master. We release from master so it is always our base branch. Feature and bugfix work happens from branches off of develop.
Expected Behavior
I would expect that develop should be versioning at 2.2.0 or 2.1.8 depending on the config.
Actual Behavior
I get a version of 0.1.0 for develop and any feature or bugfix branches.
Steps to Reproduce
I've got no clue. I tried to create a sample repo that reproduced it but have been unsuccessful. It's something about this repository but I'm not sure what.
Your Environment
I've tried it with and without a GitVersion.yml file. It doesn't seem to matter it never picks up the master branch tags in anything but when on the master branch.
Logs
develop.txt
feature.txt
main.txt
feature5.5.0.txt
Git Tags
$ git show-ref --tags
e0cd611e6686fba223efa4fdc99ac77c42eafb85 refs/tags/1.0.25
8f3e89a421b90265f6b050310293d36a9e90b687 refs/tags/2.0.0
622488d8f32c81da404db55f978bd5bdc0f3a98a refs/tags/2.0.1
c0b1c7780694712afac0d1202ceaa0cf7bf39bad refs/tags/2.0.2
a27a1c51063dfbaae08dc5470fef3b2a8104506b refs/tags/2.0.3
b0adffc6e1b52eed158a943dd0a83268664c7489 refs/tags/2.0.4
b8504f4f60fc3844d5a6d5a0b08fddbf86503468 refs/tags/2.0.5
25ee54514d900e2da0034ba56904fd59b7b85c79 refs/tags/2.0.6
3d3f6774f487237881a54988597c4d96a0e6606f refs/tags/2.1.1
22a5a03cc0234dfa86005bacde7b276e487c8c39 refs/tags/2.1.2
8020f2e2344034260b7836ad7faee0afe4abdea4 refs/tags/2.1.3
8071e0e9eed20a673f3db6b8b9c297137cd33ddd refs/tags/2.1.4
ffba6a78688091df1776ba6af7c795008aac15a5 refs/tags/2.1.5
a9db636ca40ba73f82855b463f450dfa11bceb3c refs/tags/2.1.6
7175b7511c2e23bb09cfa075579eee83600d8794 refs/tags/2.1.7
The text was updated successfully, but these errors were encountered: