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

# Change settings for one pull request

> Run a single review with different settings, add settings in the pull request description, or skip a pull request, without touching committed configuration.

You can change review behavior for one pull request without editing your configuration. Use a comment command for one run, the description for settings that stay with the pull request, or `@coderabbitai ignore` to skip it.

## Before you start

* Write each command alone on its line, with flags allowed. Extra text such as `review please` stops CodeRabbit from recognizing it, and a command inside a fenced code block doesn't count.
* Know which settings a pull request can't change. See [Enforce settings teams can't change](https://docs.coderabbit.ai/configuration/guides/enforce.md).

## Run one review with different settings

Post a comment with the command on its own line, followed by a fenced `yaml` block. CodeRabbit validates the block against the V2 schema and applies it to that review only.

````text theme={null}
@coderabbitai review --with-config
```yaml
inheritance: true
reviews:
  profile: assertive
```
````

The command also works as `@coderabbitai full review --with-config`. It works whether or not automatic reviews are on, and it counts toward the review rate limit. Nothing in the committed configuration changes.

> [!WARNING]
>
> Without `inheritance: true`, the block replaces the repository's resolved configuration for that review. Every key you leave out uses the schema default, not the repository's value. Global overrides are still applied on top. Add `inheritance: true` to keep the rest of the configuration.

The block can't change merge or security risk instructions, `allow_author_approval`, or approval risk limits and `overrides`. To add `knowledge_base.linked_repositories`, you need write access to the pull request's repository and read access to each added repository. Cross-repository entries in `knowledge_base.code_guidelines.filePatterns` are rejected.

## Add settings in the pull request description

Put the line `@coderabbitai configuration override` in the description, immediately followed by a fenced `yaml` block. You can add several blocks. Unlike a `--with-config` block, a description block always merges with `inheritance: true` onto the base configuration.

````text theme={null}
@coderabbitai configuration override
```yaml
reviews:
  review_details: true
```
````

| Key | Accepted from |
| - | - |
| `reviews.review_details` | Every pull request, including forks |
| `reviews.path_instructions` | [Trusted](https://docs.coderabbit.ai/configuration/branch.md#who-counts-as-trusted) pull requests from a branch in the same repository |
| `knowledge_base.code_guidelines.filePatterns` | Same as `reviews.path_instructions` |

A block with any other key is rejected as a whole: none of its settings apply, and the pull request shows an error. Path instructions for paths that are already configured are skipped. File patterns add to the configured ones. A description block can't change approval policy.

## Preview a configuration change not yet merged

To try a configuration change before it merges, comment `@coderabbitai review --preview-config` on the draft pull request that contains it. CodeRabbit runs an isolated full review with the pull request head's configuration and labels it non-authoritative. It doesn't update the pull request's review state, and automatic approvals stay off. You need write access, the pull request must come from your repository, and the configuration must parse. The command is listed for GitHub and GitHub Enterprise Server.

## Skip or pause one pull request

| Where you write `@coderabbitai ignore` | Effect |
| - | - |
| In the pull request description | Automatic reviews stop while the line stays. Chat and commands still work. Delete the line to resume from the next commit. |
| In a comment | Pauses reviews for that pull request. |

`@coderabbitai pause` and `@coderabbitai resume` comments pause and resume the review stream. For how the description keyword interacts with manual reviews and other skip rules, see [Skip one pull request](https://docs.coderabbit.ai/pr-reviews/when-reviews-run.md#skip-one-pull-request).

## Force a review that configuration skips

`@coderabbitai full review` runs even when configuration skips the pull request, for example for drafts, ignored authors or disabled automatic reviews. It can't override a locked conversation, a bot author without a seat, or a pull request with no reviewable files.

## Check the result

After the review posts, expand **Run configuration** in **Review info**, or post `@coderabbitai configuration`. See [Check which configuration a review used](https://docs.coderabbit.ai/configuration/guides/check-effective-configuration.md).

## What's next

> [card] [Validate and test a change](https://docs.coderabbit.ai/configuration/guides/validate-and-test.md)
>
> Try a configuration change before it reaches your team.

> [card] [Control when reviews run](https://docs.coderabbit.ai/pr-reviews/when-reviews-run.md)
>
> Set which pull requests CodeRabbit reviews automatically.

> [card] [Review commands](https://docs.coderabbit.ai/guides/commands.md)
>
> See every `@coderabbitai` command.


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