> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Find out why a pull request wasn't reviewed

> Work out why CodeRabbit didn't review or comment on a pull request, and fix the setting, seat, installation or limit that caused it.

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](https://docs.coderabbit.ai/pr-reviews/status-check.md) 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](https://docs.coderabbit.ai/configuration/guides/check-effective-configuration.md).

**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.

```mermaid theme={null}
flowchart TD
  A[Pull request event] --> B{Author ignored?}
  B -- yes --> X[Skipped]
  B -- no --> C{Labels allow it?}
  C -- no --> X
  C -- yes --> D{Title keyword?}
  D -- yes --> X
  D -- no --> E{Reviews enabled, or opted in?}
  E -- no --> X
  E -- yes --> F{Incremental review allowed?}
  F -- no --> X
  F -- yes --> G{Draft allowed?}
  G -- no --> X
  G -- yes --> H{Base branch covered?}
  H -- no --> X
  H -- yes --> R[Review runs]
```

## Find the cause

> [accordion] Automatic reviews are off
>
> **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](https://docs.coderabbit.ai/pr-reviews/when-reviews-run.md).

> [accordion] The pull request is a draft
>
> CodeRabbit skips drafts unless `drafts` is `true`. Set it, or mark the pull request ready for review.

> [accordion] The base branch isn't covered
>
> 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/.*$`.

> [accordion] The labels exclude the pull request
>
> 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.

> [accordion] The title contains a skip keyword
>
> `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](https://docs.coderabbit.ai/pr-reviews/when-reviews-run.md#how-coderabbit-decides).

> [accordion] The author is ignored
>
> `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`](https://docs.coderabbit.ai/pr-reviews/when-reviews-run#what-to-enter-in-ignore_usernames). Remove the author from the list or comment `@coderabbitai review`.

> [accordion] Incremental review is off
>
> With `auto_incremental_review: false` (V3: `incremental_review`), CodeRabbit reviews the first open only. Later pushes wait for `@coderabbitai review`.

> [accordion] Reviews are paused
>
> **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](https://docs.coderabbit.ai/pr-reviews/when-reviews-run.md#skip-one-pull-request).

> [accordion] No files are left to review
>
> 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](https://docs.coderabbit.ai/pr-reviews/which-files.md).

> [accordion] The author has no seat, or the plan doesn't cover it
>
> 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](https://docs.coderabbit.ai/management/seat-assignment.md) and [Plans and pricing](https://docs.coderabbit.ai/management/plans.md).

> [accordion] CodeRabbit isn't installed or can't reach the repository
>
> **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:
>
> | Platform | Where to check |
> | - | - |
> | GitHub | [Authorize CodeRabbit with your GitHub account](https://docs.coderabbit.ai/platforms/github-com.md#authorize-coderabbit-with-your-github-account) |
> | GitHub Enterprise Server | [Troubleshooting](https://docs.coderabbit.ai/platforms/github-enterprise-server.md#troubleshooting) |
> | GitLab.com | [Webhook issues](https://docs.coderabbit.ai/platforms/gitlab-com.md#webhook-issues) |
> | Self-managed GitLab | [Webhooks](https://docs.coderabbit.ai/platforms/self-hosted-gitlab.md#webhooks) |
> | Bitbucket Cloud | [Webhooks](https://docs.coderabbit.ai/platforms/bitbucket-cloud.md#webhooks) and [Troubleshooting](https://docs.coderabbit.ai/platforms/bitbucket-cloud.md#troubleshooting) |
> | Bitbucket Data Center | [Troubleshooting](https://docs.coderabbit.ai/platforms/bitbucket-data-center.md#troubleshooting) |
> | Azure DevOps | [Service hooks (webhook) permission](https://docs.coderabbit.ai/platforms/azure-devops.md#step-4-grant-the-required-permissions) |

> [accordion] A rate limit stopped the review
>
> **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](https://docs.coderabbit.ai/management/rate-limits.md).

> [accordion] CodeRabbit couldn't read the configuration
>
> **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](https://docs.coderabbit.ai/configuration/guides/troubleshoot.md).

## 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](https://docs.coderabbit.ai/pr-reviews/status-check.md).
* Automatic review rules apply to every Git platform.

**All settings:** [`reviews.auto_review` in the configuration reference](https://docs.coderabbit.ai/reference/configuration#param-reviews-auto-review).

## What's next

> [card] [Control when reviews run](https://docs.coderabbit.ai/pr-reviews/when-reviews-run.md)
>
> Change the settings behind each skip.

> [card] [Check which configuration a review used](https://docs.coderabbit.ai/configuration/guides/check-effective-configuration.md)
>
> Print the resolved configuration for a repository.

> [card] [Review rate limits](https://docs.coderabbit.ai/management/rate-limits.md)
>
> See how reviews are counted and refilled.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.