Correct the construction of the refname #27
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
The refName that is generated for the RefUpdated event for tags contains the prefix "refs/tags" unlike other RefUpdated events. This attempts to ensure that the correct RefName is always produced.
|
I looked at gerrit code and refs/*/ is omited from refName in the RefUpdate event only for heads refs so it safe to assume that if refName does not start with refs, it's a head refs. +1 |
rsandell
added a commit
that referenced
this pull request
Oct 26, 2014
Correct the construction of the refname
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.
The refName that is generated for the RefUpdated event
for tags contains the prefix "refs/tags" unlike other
RefUpdated events.
This attempts to ensure that the correct RefName is always
produced.