Fix Claude Code Review workflow comment tooling#18
Conversation
|
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 modernizes the Claude Code Review workflow by replacing the deprecated sticky comment mode with direct GitHub comment integration. The changes include:
The workflow now produces more natural PR review output with both top-level comments and inline code annotations, matching the fix previously applied in the hichee-data repository. Confidence Score: 5/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[PR Event Triggered] --> B[Checkout Repository]
B --> C[Run Claude Code Action]
C --> D{Review PR}
D --> E[Use gh pr comment<br/>for top-level feedback]
D --> F[Use mcp__github_inline_comment__create_inline_comment<br/>for inline code comments]
E --> G[Post to PR]
F --> G[Post to PR]
G --> H[Review Complete]
Last reviewed commit: b1f0c73 |
This ports the Claude Code review workflow fix from shakacode/hichee-data#367:
claude_args --allowedToolsThis makes Claude review output appear as top-level and inline PR comments.