Fix Claude Code Review workflow comment tooling#47
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 updates the Claude Code review workflow to use native GitHub PR comments instead of sticky comments. The changes include:
The changes align with the approach from shakacode/hichee-data#367 and should provide better integration with GitHub's native PR comment system. Confidence Score: 5/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[PR Event: opened/synchronize/ready_for_review/reopened] --> B[Checkout Repository]
B --> C[Run Claude Code Review Action]
C --> D{Review Type}
D -->|Top-level feedback| E[gh pr comment]
D -->|Inline code issues| F[mcp__github_inline_comment__create_inline_comment]
E --> G[Native GitHub PR Comments]
F --> G
G --> H[Review Visible on PR]
style C fill:#f9f,stroke:#333,stroke-width:2px
style G fill:#bfb,stroke:#333,stroke-width:2px
Last reviewed commit: 3cf5278 |
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.