Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
GH-133410: Use commit hashes for change detection#133416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
d530e74
intopython:mainUh oh!
There was an error while loading.Please reload this page.
Thanks@AA-Turner for the PR, and@ambv for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Thanks@AA-Turner for the PR, and@ambv for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
)(cherry picked from commitd530e74)Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
)(cherry picked from commitd530e74)Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
GH-133426 is a backport of this pull request to the3.12 branch. |
GH-133427 is a backport of this pull request to the3.13 branch. |
Also needs backporting to 3.12 so the CI isn't skipped there. |
hugovk commentedMay 5, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I believe this broke change detection in personal/forked branches prefixed with e.g. |
Oh yes, let's fix that :) |
Similarly, it's broken on the upstream 3.12-3.14 branches, for the post-merge runs: |
Let's continue in the issue,#133410. |
Uh oh!
There was an error while loading.Please reload this page.
As seen recently, if the pull-request branch on a fork repository has the same name as the target branch on the upstream repository, the branches shadow each other when set up by
@actions/checkout
, meaning that change detection passes with no changes having occured.This changes to instead perform the
git diff
with the commit SHA of the head commit. This is slightly tricky due to what GitHub exposes, but in short, we always compare the tip of the PR branch (fork) against the default branch (upstream).A
cc@JelleZijlstra
Tools/build/compute-changes.py
looks at the wrong branches #133410