adds optional 'match' flag to git describe #37
Merged
Conversation
This file contains 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
optional unless the user sets glob wildcard(s)
ThadHouse
approved these changes
Oct 23, 2023
ThadHouse
approved these changes
Oct 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds the option to specify "match" wildcards for git describe.
Default behavior without match globs specified is unchanged and will still return an empty version if the latest annotated tag does not follow the implemented semver requirements.
Adding a match wildcard is useful during dev or local builds if there are other formats of annotated tags between the latest commit and the last valid version tag.
This does NOT change what version formats the plugin will process; the same valid tag format is still required.