Repository navigation
Conversation
Owner
Author
|
@coderabbitai full review |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…ate limit At its included review limit, CodeRabbit leaves a check run on the head concluded SKIPPED, titled "Review skipped", with no reason of its own; the reason is in its reply to a review command. The gate now skips that check when the latest visible CodeRabbit reply says "Review rate limited." and no CodeRabbit review or newer reply (hidden, edited or otherwise) follows it.
bompus
force-pushed
the
fix/gate-skipped-coderabbit-ratelimit
branch
from
October 27, 2026 05:35
f21fe04 to
6376702
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When CodeRabbit is at its included review limit it answers a review command with a comment ("Review rate limited.") and leaves a check run on the head commit that concluded SKIPPED, titled "Review skipped", with no reason of its own. The gate accepted the rate limit only as a commit status, so it refused the check run as open feedback and the pull request could not land while the limit lasted (found on bompus/swarmail#206).
The gate now skips CodeRabbit, naming the reason, when its check run on the head concluded SKIPPED with that title, its latest reply to a review command said "Review rate limited.", and it has posted no review since. The reply may precede the head commit, since a push made while limited gets a skipped check without a new reply. A newer reply that says anything else (including one a person edited), a later CodeRabbit review, no reply, a hidden or non-CodeRabbit reply, another title or another conclusion still refuse.
Verified:
bun run checkexits 0; the 185 hr-pr-followup tests pass, and the new test fails without the change. Run against bompus/swarmail#206 the gate now prints "none open (2 review bot(s) skipped)". A GPT-6.1 Sol xhigh review found ways an old rate-limit reply could outlive newer evidence (a later review, a person-edited failure, a failure posted after the check, a newer file-count skip summary, a hidden newer failure); each is fixed and covered by tests.