[24.x] Fix Get-CurrentBranch to always rely on git (and not GITHUB_REF env variable) #951
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
…ariable) Fix `Get-CurrentBranch` to always rely on git (and not GITHUB_REF env variable) `$env:GITHUB_REF` is not the same as the checked out branch. `$env:GITHUB_REF` is the branch the workflow is running on. Fixes AB#525684
github-actions
bot
added
the
Build: scripts & configs
aholstrup1
approved these changes
Apr 17, 2024
tomasmsft
approved these changes
Apr 18, 2024
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.
Fix
Get-CurrentBranchto always rely on git (and not GITHUB_REF env variable)$env:GITHUB_REFis not the same as the checked out branch.$env:GITHUB_REFis the branch the workflow is running on.Fixes AB#525684