Fix: Use pull_request_target to resolve 403 error in peer review check #4834
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
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Co-authored-by: DonnieBLT <[email protected]>
Copilot
AI
changed the title
[WIP] Fix issue with posting peer review comments
Fix: Use pull_request_target to resolve 403 error in peer review check
Nov 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 peer review workflow was failing with HTTP 403 "Resource not accessible by integration" when posting comments to PRs from forks. The
pull_requesttrigger runs in the fork's context with read-onlyGITHUB_TOKENpermissions.Changes:
pull_requesttopull_request_targetin.github/workflows/check-peer-review.ymlThe
pull_request_targettrigger runs in the base repo context, granting write permissions to post comments. This is safe since the workflow only makes GitHub API calls without executing PR code, following the same pattern asadd-comment-count-label.yml.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.