Fix Claude Code Review workflow permissions

[justin808]

Summary

• Add permissions block to the Claude Code Review caller workflow
• The reusable workflow in shakacode/.github needs issues: write, pull-requests: write, and id-token: write, but callers must explicitly grant these permissions
• Without this, the workflow fails with: "The nested job is requesting permissions but is only allowed none"

Test plan

• Verify the Claude Code Review workflow runs successfully on a new PR

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@justin808 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 6 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch jg/fix-claude-review-perms

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Updates the Claude Code Review GitHub Actions caller workflow to explicitly grant the permissions required by the reusable workflow in shakacode/.github, avoiding failures due to default “none” permissions on nested jobs.

Changes:

• Add a job-level permissions block (contents read, pull-requests write, issues write, id-token write) to the reusable workflow caller.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

With the added pull-requests: write / issues: write permissions, referencing the reusable workflow via @main increases supply-chain risk (the called workflow can change without review). Consider pinning uses: to an immutable ref (tag or commit SHA) and updating intentionally when needed.