馃懛 Fix latest-changes checkout target - #1883
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
latest-changesworkflow checkout step to use the repository default branch explicitly.pull_request_targetruns on trusted base-repository code whenactions/checkout@v7is used.Why
actions/checkout@v7refuses fork PR code in trustedpull_request_targetcontexts. For merged PR release-note workflows, the safe target is the base repository default branch.Validation
git diff --checkfor the changed workflow.tiangolo/sandbox.AI Disclaimer
Using Codex with GPT-5. Reviewed manually.