Fix Claude Code Review workflow: use built-in review#17
Conversation
The plugin-based review setup is broken — the plugin tries to call gh api via the Bash tool, which the action sandbox blocks by default. Removing in favor of the working default claude.yml (@claude mentions). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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)
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. Comment |
Greptile SummaryThis PR removes the
Confidence Score: 5/5
Important Files Changed
Last reviewed commit: 6ec6893 |
…n plugin Replace the plugin-based review (which fails because the sandbox blocks Bash tool access) with the built-in review_triggered_on and use_sticky_comment options. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The action auto-detects review mode from the pull_request trigger. Only use_sticky_comment and prompt are needed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
claude-code-review.ymlworkflow to use the built-in review instead of the broken plugin approachgh apivia the Bash tool, which the action's sandbox blocksplugin_marketplaces/plugins/promptwithreview_triggered_on: pranduse_sticky_comment: trueTest plan
🤖 Generated with Claude Code