Fix malformed sha tag - #1318
Merged
Merged
Conversation
…n whatever its shape (SHA or dotted version)
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
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.
Fixes #1317
Changes:
.12.0so the snippet pins the bare commit SHA.(GIT_TAG) [^ )]+so itreplaces the whole token whatever its shape (SHA or dotted version) and
stops at the closing paren. This should prevent partial-match leftovers
Verified the new expression against both historical shapes —
GIT_TAG 1.12.0)and
GIT_TAG f091…79d.12.0)each come out asGIT_TAG <new-sha>).