Add git-sha to rule variables, add test for the variable.#14810
Open
toots wants to merge 1 commit into
Open
Conversation
Signed-off-by: Romain Beauxis <romain.beauxis@gmail.com>
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.
This follows the discussion at: #14723
My suggestion is that since this value is used to track the exact commit being used for builds, CI run etc, it's better to be specific about what it is, i.e. a
gitcommit SHA rather than wrapping it up in any higher level semantics i.e.vcs-commit-idetc. so that the user knows exactly what they're dealing with and can use it with confidence.