feat(github): fallback on remote branch for --affected #10732
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.
Description
Fixes #9320 ;
When checking out a repo in GitHub Actions using
actions/checkout(even withfetch-depth: 0), we often do not have local branches set (forpull_request, it's likely we don't have any local branches at all).git rev-parsedoes not "fallback" naturally to a remote branch when used on a local reference.This causes the issue described in #9320, which essentially prevents GitHub Actions users from leveraging
--affected"out-of-the-box" and usingTURBO_SCM_BASE, which, in my opinion, is sub-optimal.To fix that, this PR implement a "fallback" on
origin/local_branch_nameTesting Instructions