Skip to content
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

Confused about where values come from #21

Closed
asherber opened this issue Dec 26, 2016 · 2 comments
Closed

Confused about where values come from #21

asherber opened this issue Dec 26, 2016 · 2 comments

Comments

@asherber
Copy link

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:

image

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.

@kzu
Copy link
Member

kzu commented Dec 26, 2016

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

@kzu kzu closed this as completed Dec 26, 2016
@asherber
Copy link
Author

Thanks. I did look at a detailed build log, but I must have missed it.

@devlooped devlooped locked and limited conversation to collaborators Sep 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants