-
Notifications
You must be signed in to change notification settings - Fork 133
Modify CLAUDE code review workflow settings #1261
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -15,7 +15,6 @@ jobs: | |||||||||||
| id-token: write | ||||||||||||
|
|
||||||||||||
| steps: | ||||||||||||
| # IMPORTANT: checkout BASE repo only (safe on forks) | ||||||||||||
| - name: Checkout base repo (safe) | ||||||||||||
| uses: actions/checkout@v4 | ||||||||||||
| with: | ||||||||||||
|
|
@@ -32,16 +31,14 @@ jobs: | |||||||||||
|
|
||||||||||||
| claude_args: > | ||||||||||||
| --dangerously-skip-permissions | ||||||||||||
| --max-turns 30 | ||||||||||||
| --max-turns 60 | ||||||||||||
| --allowedTools | ||||||||||||
| "Bash(gh pr view:*)" | ||||||||||||
| "Bash(gh pr diff:*)" | ||||||||||||
| "Bash(gh pr comment:*)" | ||||||||||||
|
||||||||||||
| "Bash(gh pr comment:*)" | |
| "Bash(gh pr comment:*)" | |
| "Bash(gh pr list:*)" | |
| "Bash(gh pr status:*)" | |
| "Bash(gh issue comment:*)" |
Copilot
AI
Feb 24, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The restricted cat tool permissions (from "Bash(cat:)" to "Bash(cat CLAUDE.md:)" and "Bash(cat .claude/rules/:)") improve security by preventing arbitrary file reads. However, this might be too restrictive if the reviewer needs to examine other documentation files or configuration files (like .github/workflows/*.yml for context). Verify that these restrictions won't hinder the reviewer's ability to gather necessary context.
Copilot
AI
Feb 24, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The instruction "If no issues: 0–3 improvement opportunities (only if confident)" is ambiguous. The range "0–3" suggests the reviewer can choose to provide zero improvement opportunities, but the parenthetical "(only if confident)" could be interpreted as applying only when providing opportunities or as a general qualifier. Consider clarifying this to "If no issues: provide 0–3 improvement opportunities (only suggest if confident they would be valuable)" or similar wording.
| - If no issues: 0–3 improvement opportunities (only if confident) | |
| - If no issues: provide 0–3 improvement opportunities (only suggest if confident they would be valuable) |
Copilot
AI
Feb 24, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The removal of the fallback instruction "If posting a PR comment is blocked, write the full review to the GitHub Actions job summary instead" eliminates a useful error handling mechanism. If the gh pr comment command fails due to permissions issues or API errors, the review results will be lost. Consider keeping this fallback to ensure review feedback is always captured somewhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The removed comment "# IMPORTANT: checkout BASE repo only (safe on forks)" provided valuable security context for why this step is safe in pull_request_target workflows. Removing it makes the workflow less self-documenting. Consider keeping this comment as it explains a critical security consideration.