Skip to main content
Use this page when CodeRabbit didn’t review your pull request, or when it reviewed but left no comments. Most causes are a setting you can change. A few are seats, installation or limits.

Start here

1

Look for a message on the pull request

CodeRabbit can post a status message when it skips a review, and it reports each review in the CodeRabbit check. See CodeRabbit status check for what each state means.
2

Check whether it ran and found nothing

A review with no findings shows No actionable comments were generated in the recent review. below the walkthrough. That message means the review ran.
3

Print the configuration the review used

Comment @coderabbitai configuration. See Check which configuration a review used.
4

Ask for a review by hand

Comment @coderabbitai review, or @coderabbitai full review to review every file again. CodeRabbit replies Review triggered. If a manual review also does nothing, the cause is usually not an automatic review setting. Go to seats, installation or limits.
@coderabbitai full review overrides configuration skips such as drafts, ignored authors and disabled automatic reviews. It doesn’t override a locked conversation, a bot author without a seat, or a pull request with no reviewable files.

How CodeRabbit decides

CodeRabbit checks automatic review rules in this order and skips the pull request at the first rule that excludes it.

Find the cause

Signs: nothing happens until you comment.Check that reviews.auto_review.enabled isn’t false, in your file and in the app under Reviews > Auto review. With enabled: false, a positive label in labels or a description_keyword in the description still starts a review.See Control when reviews run.
CodeRabbit skips drafts unless drafts is true. Set it, or mark the pull request ready for review.
Automatic reviews cover the default branch. base_branches adds more, and each entry is an unanchored regular expression. A pull request to release/1.2 needs an entry such as ^release/.*$.
Labels match exactly and are case-sensitive. With a positive label in labels, a pull request needs at least one of them. With a ! label, a pull request must have none of them.
ignore_title_keywords matches case-insensitively, and a keyword that starts and ends with a letter or digit matches whole words only, so WIP skips wip: add login but not wiped cache. A title containing [Snyk] is always skipped. See How CodeRabbit decides.
ignore_usernames matches exactly and case-sensitively, with no wildcards. The skip is silent. Each platform matches a different name, such as the display name on Bitbucket Cloud. On Azure DevOps, CodeRabbit converts the author’s unique name to lowercase but not your entries, so an entry with uppercase letters never matches. See What to enter in ignore_usernames. Remove the author from the list or comment @coderabbitai review.
With auto_incremental_review: false (V3: incremental_review), CodeRabbit reviews the first open only. Later pushes wait for @coderabbitai review.
Signs: the check shows Review paused.CodeRabbit pauses after auto_pause_after_reviewed_commits reviewed commits (default 5), or when someone comments @coderabbitai pause. Comment @coderabbitai resume to continue. A pull request description that contains @coderabbitai ignore also stops automatic reviews until you remove it. See Skip one pull request.
When path filters exclude every changed file, the review is skipped with the reason No files to review and the check passes. Lock-file-only and generated-code-only pull requests end this way. See Choose which files are reviewed.
CodeRabbit reviews pull requests from authors with a seat. Without one, the pull request gets a free summary with a note that the author has no seat, or that the organization reached its seat limit. An admin can assign a seat in Team Management. See Seat assignment and Plans and pricing.
Signs: no CodeRabbit check and no comment, and manual commands get no reply.CodeRabbit posts nothing when it never receives the event, for example when the app isn’t installed on the repository or a webhook was lost. It also can’t post when it lacks permission to write comments or statuses.Check the installation, webhooks and permissions on your platform’s page:
Signs: the check shows Review rate limited.CodeRabbit limits reviews per developer over rolling windows, and pushes count as review events. Comment @coderabbitai rate limit to see when reviews are available again. See Review rate limits.
Signs: no review, no comment and no check on the commit.A missing configuration file is normal, and CodeRabbit moves on to the next layer. Any other failure to read the repository, the file, the central repository or a remote configuration source makes CodeRabbit retry the review, up to 3 times. After that it drops the review and posts nothing to the pull request. Comment @coderabbitai full review to try again, and contact support if it keeps failing.An invalid configuration file is different. The review still runs with the next layers, and its summary starts with a warning that the file has a parsing error. See Fix settings that aren’t applied.

Limits and availability

  • CodeRabbit doesn’t review a GitHub merge queue commit. It reports a successful CodeRabbit check titled Pull request review passed so the queue doesn’t stall.
  • A skipped or rate-limited review leaves a required CodeRabbit check passing. No setting guarantees that every pull request gets a full review. See CodeRabbit status check.
  • Automatic review rules apply to every Git platform.
All settings: reviews.auto_review in the configuration reference.

What’s next

Control when reviews run

Change the settings behind each skip.

Check which configuration a review used

Print the resolved configuration for a repository.

Review rate limits

See how reviews are counted and refilled.