ci: stop stray review comments cancelling in-progress AI reviews#89
Conversation
|
Warning Review limit reached
More reviews will be available in 54 minutes and 28 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Gemini review skipped — non-code PR (only changed files matching |
|
Codex review skipped — non-code PR (only changed files matching |
|
Claude review skipped — non-code PR (only changed files matching |
What
Changes the AI-reviewer caller concurrency from
cancel-in-progress: trueto:Why
These callers trigger on
pull_request_review_comment, and every comment sharesthe same per-PR concurrency group. Workflow-level concurrency is evaluated at run
creation — before the reusable's preflight
@mentiongate skips a straycomment — so an unconditional
truelets any inline review comment cancel anin-progress review and leave the PR with none.
Gating cancellation on
pull_request(open/ready) events means stray reviewcomments queue behind a running review and no-op instead of killing it, while
open/ready dedup is preserved.
Same class of bug as google-github-actions/run-gemini-cli#195.
🤖 Generated with Claude Code