Embed commit in version string when developing - #143
Merged
Conversation
istathar
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For non-release builds, embed the commit (and, if present, dirty status) in the version string. This allows a developer to know whether they are running a release, a build from a fully committed tree or, a local work-in-progress.
The result is that a release build will show a version of
v0.6.5being the tag name. A build from a Git checkout with work done since the tag will be the Cargo package version and Git commit hashv0.6.6+24824ba, and a build from a checkout with locally uncommitted files will show asv0.6.6+24824ba.dev.