Support forks, release candidates, and dirty versions in GitVersion parsing #2250
+1,437
−99
Conversation
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
mjcheetham
force-pushed
the
gitver
branch
4 times, most recently
from
c81745e to
aea46ed
Compare
Enhance the GitVersion type to be aware of different forks of Git including Git for Windows, Microsoft, and Apple. Also add support for release candidates found in the version string - these can appear as either a -rcN or .rcN format depending on if this is a tag or a build version. We support both types. Finally also capture the Commit ID from a dirty build version, i.e, <major>.<minor>.<patch>.g<sha> Signed-off-by: Matthew John Cheetham <mjcheetham@outlook.com>
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.
Enhance the
GitVersiontype to be aware of different forks of Git including Git for Windows, Microsoft, and Apple.Also add support for release candidates found in the version string - these can appear as either a
-rcNor.rcNformat depending on if this is a tag or a build version. We support both types.Finally also capture the Commit ID from a dirty build version, i.e,
<major>.<minor>.<patch>.g<sha>Extensive tests cover all known version formats spotted in the wild, including: