New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version is different on a fresh repo clone #1395
Comments
Have you tried to do a |
I tried Let me add, if it points in the right direction, that I'm using gitflow workflow and the above version numbers are generated when a It seems as if version number was calculated differently for the 'old' and the 'fresh' repo. I have run
I don't fully understand why this is happening. 'Old repo':
'Fresh repo':
|
The same version of GitVersion is running in both repositories? Task or |
All outputs above come from the same Additionally, consistent results occur when MSBuild task is used. (GitVersionTask version="4.0.0-beta0012") Also, I verified that another fresh clone works same as the 'previous fresh' clone. I can of course work on one of the fresh clones from now on. That said, I am not sure why it works this way and how to avoid it in the future and what impact it may have on CI. My guess would be this is purely a git thing, but for the fact that |
I have no idea what might be going on here. If a fresh clone fixes the problem for you, that's an easier fix than trying to figure out the underlying reason why GitVersion is being confused. |
On a certain branch in a local repo I was working on,
gitversion
command returnsMajoMinorPatch=0.1.0
. However, when I make a fresh clone of the same repo,gitversion
produces2.1.0
.Both numbers definitely make sense assuming the first repo is out-of-date. That said, I tried:
.git/gitversion_cache
folderbut the version remains at
0.1.0
.Am I missing the correct way to sync local repo with remote? Was does
gitversion
expect me to do?The text was updated successfully, but these errors were encountered: