-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: use base and head SHAs from context in lint-build-commits workflow #32140
Conversation
ae7643e
to
f1773f2
Compare
f1773f2
to
b238aaf
Compare
Testing PR here: #32143 |
22a909b
to
222c303
Compare
Instead of querying the GitHub API for the parent SHA, use the base and head SHA provided by the github.event.pull_request context. This works fine because the workflow only runs on pull requests. Also use a loop and git checkout instead of git rebase to avoid potential issues with merge conflicts in the presence of merge commits in the PR. Signed-off-by: Tobias Klauser <[email protected]>
222c303
to
9496da4
Compare
Example of a failing run: https://github.com/cilium/cilium/actions/runs/8892417966/job/24416427312?pr=32143 Example of a passing run: https://github.com/cilium/cilium/actions/runs/8892565244/job/24416905970?pr=32143 Marking ready for review. |
/test |
@tklauser did you still plan to open the backports for this PR? :) |
@julianwiedmann sorry for the delay, I'll work on these backports this week. |
Instead of querying the GitHub API for the parent SHA, use the base and head SHA provided by the github.event.pull_request context. This works fine because the workflow only runs on pull requests.
Also use a loop and git checkout instead of git rebase to avoid potential issues with merge conflicts in the presence of merge commits in the PR.