Fix branch name detection #1642
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
carolynvs
force-pushed
the
fix-branch-name-detection
branch
2 times, most recently
from
976b4b6 to
1cf8f12
Compare
Merged
|
/azp run porter |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Don't assume the first branch name will work. Loop through matching refs, excluding tags, and look first for main and then for release/v*. Signed-off-by: Carolyn Van Slyck <[email protected]>
carolynvs
force-pushed
the
fix-branch-name-detection
branch
from
1cf8f12 to
e458738
Compare
vdice
approved these changes
Jun 15, 2021
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.
Don't assume the first branch name will work. Loop through matching refs, excluding tags, and look first for main and then for release/v*. This better accounts for how the git repo looks in CI.