Allow Claude to code review PRs from forks #1001
Merged
+35
−1
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
…oesn't change the existing Claude workflow. * Added claude_pr_review.yml
…tion that keeps secrets from being accessed on PRs from forks. We will have to request reviews manually. * Modify claude.yml 1. Added "Get PR details" step (NEW - lines 28-51) This new step runs ONLY when the trigger is a PR-related comment. It: - Detects if it's a PR comment vs regular issue - Fetches the PR information using GitHub API - Extracts the fork's repository name and commit SHA - Sets them as outputs (steps.pr.outputs.sha and steps.pr.outputs.repo) Why? The original workflow couldn't see fork PR code because it only checked out the main repo. 2. Split checkout into TWO conditional steps (CHANGED - lines 53-62) Before: One checkout step that always checked out main repo with fetch-depth: 1 After: Two checkout steps: - "Checkout PR branch" - Runs if PR details were fetched successfully, checks out the fork's PR branch - "Checkout repository" - Runs otherwise (for regular issues), checks out main repo Why? Need different checkout behavior for PRs (checkout fork) vs issues (checkout main). 3. Changed fetch-depth from 1 to 0 (CHANGED) Before: fetch-depth: 1 (only latest commit) After: fetch-depth: 0 (full git history) Why? Claude Code needs more context to understand the codebase and provide better reviews. Summary The original workflow could only see the main repo's code. When you commented @claude on a fork PR, it would review the wrong code! These changes make it check out the actual PR branch from the fork when reviewing PRs, while keeping the original behavior for regular issues.
cliffhall
changed the title
olaservo
approved these changes
Jan 6, 2026
Member
olaservo
left a comment
olaservo
left a comment
There was a problem hiding this comment.
Thanks, looking forward to trying this out.
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.
Summary
Allow Claude to do code reviews safely from forks.
Type of Change
Changes Made
Modified claude.yml
This new step runs ONLY when the trigger is a PR-related comment. It:
Why? The original workflow couldn't see fork PR code because it only checked out the main repo.
Before: One checkout step that always checked out main repo with fetch-depth: 1
After: Two checkout steps:
Why? Need different checkout behavior for PRs (checkout fork) vs issues (checkout main).
Before: fetch-depth: 1 (only latest commit)
After: fetch-depth: 0 (full git history)
Why? Claude Code needs more context to understand the codebase and provide better reviews.
Summary
The original workflow could only see the main repo's code. When you commented @claude on a fork PR, it would review the wrong code! These changes make it check out the actual PR branch from the fork when reviewing PRs, while keeping the original behavior for regular issues.
Related Issues
Fixes #1000
Testing
Test Results and/or Instructions
Screenshots are encouraged to share your testing results for this change.
Checklist
npm run prettier-fix)Breaking Changes
Nope.