fix(ci): use pull_request_target for fork PR secret access#1137
Merged
Conversation
chaodu-agent
force-pushed
the
fix/pr-review-target
branch
from
7353dac to
4c40380
Compare
thepagent
approved these changes
Jun 18, 2026
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
2 participants
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.
The app token fix (#1136) still fails for fork PRs because
pull_requestevents don't expose secrets to fork workflows.Switch to
pull_request_targetwhich runs in the base repo context with full secret access. This is safe because the workflow never checks out or executes PR code — it only sets commit statuses and triggers a Discord webhook.