We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Getting my feet wet with this package, and I'm confused about where things are coming from. I have a project that looks like this:
When I build this with no GitInfo.txt and no customization, I get:
GitBranch=master; GitCommit=8860bcb; GitSha=8860bcb59f1e83db93e6aea90d1e8928bb1e692f; GitBaseVersion=0.1.0; GitBaseVersionSource=; GitBaseVersionMajor=0; GitBaseVersionMinor=1; GitBaseVersionPatch=0; GitCommits=0; GitTag=v2.1-1-g8860bcb; GitBaseTag=v2.1; GitSemVerMajor=0; GitSemVerMinor=1; GitSemVerPatch=0; GitSemVerLabel=; GitSemVerDashLabel=; GitSemVerSource=Default
GitInfo sees the tag, so why is it using the default 0.1.0 as the BaseVersion and SemVer?
Shouldn't GitCommits be 1, since I'm 1 commit ahead of the tag?
Thanks for any clarification.
The text was updated successfully, but these errors were encountered:
The tag version is not a valid semver, which is why it isn't used. It should be v2.1.0.
A detailed build log would show that, IIRC
Sorry, something went wrong.
Thanks. I did look at a detailed build log, but I must have missed it.
No branches or pull requests
Getting my feet wet with this package, and I'm confused about where things are coming from. I have a project that looks like this:
When I build this with no GitInfo.txt and no customization, I get:
GitInfo sees the tag, so why is it using the default 0.1.0 as the BaseVersion and SemVer?
Shouldn't GitCommits be 1, since I'm 1 commit ahead of the tag?
Thanks for any clarification.
The text was updated successfully, but these errors were encountered: