Repository navigation
feat: skip PRs with CHANGES_REQUESTED review decision - #222
Conversation
Adds an early-exit check alongside the existing CI guards so the cascade skips any PR where a human reviewer has already requested changes. Reviewing those PRs before the author responds wastes tokens and creates confusing parallel feedback threads. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
|
No description provided. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 275b8cb57e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Code Review
This pull request updates the scripts/review-one-pr.sh script to include the reviewDecision field when fetching pull request data. It adds logic to skip the review process if changes have already been requested, ensuring the script waits for an author response before proceeding. I have no feedback to provide as there were no review comments.
|
No description provided. |
…views Two issues addressed from Codex P2 feedback: 1. FORCE_REVIEW bypass: mention-triggered and force_review=true runs now bypass the CHANGES_REQUESTED skip, so authors can explicitly request a re-review after addressing feedback. 2. Stale review guard: only skip when a CHANGES_REQUESTED review targets the current head SHA. On repos without automatic stale-review dismissal, reviewDecision stays CHANGES_REQUESTED after new commits — the cascade now re-engages when the author has pushed new work. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
|
|
No description provided. |
|
No description provided. |



Summary
reviewDecisionto the initialgh pr viewsnapshot (same API call asheadRefOidandstatusCheckRollup— no extra cost)REVIEW_DECISIONalongside the existing CI status linereviewDecision == CHANGES_REQUESTED— positioned after the CI guards so cheapest/broadest checks run firstWhy
Reviewing a PR that already has "Changes Requested" from a human wastes tokens and produces confusing parallel feedback threads. The author needs to respond to existing feedback first; the bot re-engages after a new push (which resets the
reviewDecision).Not changed
CI skipping (failing/pending → exit 100) was already implemented in
review-one-pr.sh— no changes needed there.Test plan
workflow_dispatchwith a PR URL that has an open "Changes Requested" review — confirm log showsskip: changes requestedand the PR is counted as a no-op (not againstMAX_PRSbudget)REVIEW_DECISION=APPROVEDis logged and no skip fires🤖 Generated with Claude Code