This reference is automatically generated from the CodeRabbit configuration schema. Last updated: October 19, 2026
.coderabbit.yaml file in your repository root. This reference covers all available configuration options with clear property names and examples.
Quick Start
Get started with basic configuration
YAML config examples
Browse example configurations
Configuration sections
General settings
Configure general settings
Code reviews
Configure automatic code reviews, tools, and review behavior
Chat
Configure interactive chat features
Knowledge base
Configure knowledge base features
Code generation
Configure code generation settings
Issue enrichment
Configure automatic Issue enrichment and planning
General settings
enum
default:"en-US"
Set the language for reviews by using the corresponding ISO language code.One of the following:
de, de-DE, de-AT, de-CH, en, en-US, en-AU, en-GB, en-CA, en-NZ, en-ZA, es, es-AR, fr, fr-CA, fr-CH, fr-BE, nl, nl-BE, pt-AO, pt, pt-BR, pt-MZ, pt-PT, ar, ast-ES, ast, be-BY, be, br-FR, br, ca-ES, ca, ca-ES-valencia, ca-ES-balear, da-DK, da, de-DE-x-simple-language, el-GR, el, eo, fa, ga-IE, ga, gl-ES, gl, it, ja-JP, ja, km-KH, km, ko-KR, ko, pl-PL, pl, ro-RO, ro, ru-RU, ru, sk-SK, sk, sl-SI, sl, sv, ta-IN, ta, tl-PH, tl, tr, uk-UA, uk, zh-CN, zh, zh-TW, crh-UA, crh, cs-CZ, cs, nb, no, nl-NL, de-DE-x-simple-language-DE, es-ES, it-IT, fa-IR, sv-SE, de-LU, fr-FR, bg-BG, bg, he-IL, he, hi-IN, hi, vi-VN, vi, th-TH, th, bn-BD, bnstring
default:""
Set the tone of reviews and chat. Example: ‘You must talk like Mr. T. I pity the fool who doesn’t!’
Max length: 250
boolean
default:false
Enable early-access features.
boolean
default:true
Enable free tier features for users not on a paid plan.
boolean
default:false
Inheritance: Use parent settings for any values not defined here. Inheritance only propagates upward if enabled at each level.Learn more: Configuration inheritance
Reviews
Settings related to reviews.enum
default:"chill"
Set the review profile: quiet for only the most important feedback, chill for balanced feedback, assertive for more feedback (which may feel nitpicky).One of the following:
quiet, chill, assertivequiet: Posts only the most important comments inline and groups the other review comments in the review summary.chill: Balanced feedback.assertive: More feedback, which may feel nitpicky.
boolean
default:false
Automatically approve when CodeRabbit’s comments are resolved, the latest commit has been reviewed, and no pre-merge checks are failing. Note: In GitLab, all discussions must be resolved.Learn more: Request changes workflow
boolean
default:true
Allow Author Approval: Controls whether pull request authors can use
@coderabbitai approve and @coderabbitai resolve on their own pull requests. When disabled, anyone other than the author can still use them, provided CodeRabbit can identify both the commenter and the author. The pull request’s branch configuration cannot re-enable this setting.Learn more: Request changes workflowboolean
default:true
Generate a high-level summary of the changes in the PR description or walkthrough.Learn more: PR Summaries
string
default:""
By default, CodeRabbit generates release notes in the description. Use this to customize the summary content and format. Example: ‘Create concise release notes as a bullet-point list, followed by a Markdown table showing lines added and removed by each contributing author.’ Note: Use
high_level_summary_in_walkthrough to place the summary in the walkthrough instead of the description.Learn more: PR Summariesstring
default:"@coderabbitai summary"
Placeholder in the PR description that CodeRabbit replaces with the high-level summary. If
high_level_summary is false, the summary is still generated when this placeholder is present.Learn more: PR Summariesboolean
default:false
Include the high-level summary in the walkthrough comment.Learn more: PR Summaries
string
default:"@coderabbitai"
Add this keyword to the PR title to auto-generate a title.
string
default:""
Auto Title Instructions: Customize how CodeRabbit generates the PR title.
boolean
default:true
Post review status messages (e.g., when a review is skipped) in the walkthrough summary comment.Learn more: PR Walkthroughs
boolean
default:true
Post review information such as the configuration used, reviewed commits, and skipped files.
boolean
default:false
Post review details (ignored files, extra context used, suppressed comments, etc.).
boolean
default:true
Publish the canonical user-facing review status and progress updates (GitHub progress reports/check runs today; other platform equivalents may follow).
boolean
default:true
Mirror review progress using legacy commit statuses for compatibility with required checks and existing automations. Applies when
review_progress is disabled or the newer progress surface is unavailable for the provider or deployment. Azure DevOps currently uses this fallback even when review_progress is enabled.Learn more: Azure DevOpsboolean
default:false
On review errors, fail the active outward review status surface. When review_progress is enabled this applies to progress reporting; otherwise it applies to the legacy commit-status mirror when enabled.
boolean
default:true
Wrap the walkthrough in a Markdown collapsible section.Learn more: PR Walkthroughs
boolean
default:true
Include a summary of the changed files in the walkthrough.Learn more: PR Walkthroughs
boolean
default:true
Include sequence diagrams in the walkthrough.Learn more: PR Walkthroughs
boolean
default:true
Include an estimated code review effort in the walkthrough.Learn more: PR Walkthroughs
boolean
default:true
Include an assessment of how well the changes address linked issues in the walkthrough.Learn more: PR Walkthroughs
Include potentially related issues in the walkthrough.Learn more: PR Walkthroughs
Related PRs: Include potentially related PRs in the walkthrough.Learn more: PR Walkthroughs
boolean
default:true
Suggest labels based on the changes, and include them in the walkthrough.Learn more: PR Walkthroughs
array of object
default:[]
Labeling Instructions: Define allowed labels and when to suggest them. When provided, CodeRabbit suggests only from this list (still informed by prior PRs); when empty, suggestions rely entirely on prior PRs.
.coderabbit.yaml
object
Mutually Exclusive Groups: Define labels that should not coexist. Example:
{ risk: ['critical', 'high', 'medium', 'low'] }.boolean
default:false
Automatically apply suggested labels to the PR.
boolean
default:true
Suggest reviewers based on the changes, and include them in the walkthrough.Learn more: PR Walkthroughs
boolean
default:false
Automatically assign the suggested reviewers to the PR.Learn more: PR Walkthroughs
array of object
default:[]
Reviewer Instructions: Map reviewers (users or team) to PR scenarios where they should be assigned. When empty, suggestions rely on prior PRs. Team handles are supported only on GitHub.Learn more: PR Walkthroughs
boolean
default:true
Post a fortune message while the review is running.Learn more: PR Walkthroughs
boolean
default:false
Generate a poem in the walkthrough comment.Learn more: PR Walkthroughs
boolean
default:true
Prompt for AI Agents: Include the ’🤖 Prompt for AI Agents’ section in inline review comments to provide codegen instructions for AI agents.
array of string
default:[]
Specify file patterns to include or exclude in a review using glob patterns (e.g.,
!dist/**, src/**). These patterns also apply to ‘git sparse-checkout’, including specified patterns and ignoring excluded ones (starting with ’!’) when cloning the repository.Learn more: Path-based review instructions.coderabbit.yaml
array of object
default:[]
Path Instructions: Add path-specific guidance for code review.Learn more: Path-based review instructions
.coderabbit.yaml
boolean
default:true
Abort the in-progress review if the PR is closed or merged.
boolean
default:false
Disable caching of code and dependencies; fetch them fresh on each run.Learn more: Caching
array of object
default:[]
Custom Post-merge Actions: Define custom actions to run after merging. Each action needs a unique name (≤100 chars) and a deterministic prompt (≤10,000 chars).Learn more: Post-Merge Actions
Anti-Slop
reviews.slop_detection
Settings for detecting spam or low-quality pull requests and merge requests. Private repositories require the Essentials plan or higher. Public GitHub, GitLab, and Bitbucket repositories are eligible on all plans. Author exemptions, integration availability, labeling, and rechecks vary by platform.
Learn more: Slop Detection
boolean
default:true
Enable or disable slop and low-quality PR detection.
boolean
default:false
Include authors otherwise exempt because of their repository relationship, including same-repository pull requests on Azure DevOps and Bitbucket. Recognized automation accounts remain exempt.Learn more: Slop Detection
string
Label to apply when a request is classified as spam or slop on platforms that support labeling. Requests with this label are eligible for analysis on subsequent reviews on GitHub, GitLab, and Azure DevOps. Bitbucket does not support label-based rechecks.Learn more: Slop Detection
Min length: 1
Auto review
reviews.auto_review
Learn more: Automatic review controls
boolean
default:true
Automatic Review: Review PRs automatically.
string
default:""
Keyword in the PR description that triggers a review when automatic reviews are disabled. If
enabled is false and this field is not empty, CodeRabbit reviews the PR only when this keyword is present in the description.boolean
default:true
Incremental Review: Re-run the review on each push.
integer
default:5
Auto Pause After Reviewed Commits: Pause automatic reviews after this many reviewed commits since the last pause. Set to 0 to disable.
Min: 0, Max: 9007199254740991
array of string
default:[]
Skip reviews when the PR title contains any of these keywords (case-insensitive).
array of string
default:[]
Labels that control which PRs are reviewed. Labels starting with ’!’ are negative matches. Examples: [‘bug’, ‘feature’] reviews PRs with either label. [‘!wip’] reviews all PRs except those labeled ‘wip’ when automatic reviews are enabled. [‘bug’, ‘!wip’] reviews PRs labeled ‘bug’ but not ‘wip’. When
enabled is false, a positive label match (for example [‘review-ready’]) triggers a review; negative-only labels such as [‘!wip’] remain exclusion filters and do not opt PRs in by themselves..coderabbit.yaml
boolean
default:false
Include draft PRs.
array of string
default:[]
Base branches (other than the default branch) to review. Accepts regex patterns. Use ’.*’ to match all branches.Each entry is a regular expression tested against the target branch name without anchoring, so
develop also matches develop-2. Use ^ and $ to match the whole name..coderabbit.yaml
array of string
default:[]
Skip reviews for pull requests authored by these usernames. Matching is exact and case-sensitive. Bitbucket Cloud matches the author’s display name, and Azure DevOps matches their unique name, usually the sign-in email, in lowercase.Learn more: Automatic review controls
Finishing touches
reviews.finishing_touches
Learn more: Finishing Touches overview
object
Docstrings: Configure docstring generation.
object
Unit Tests: Configure unit test generation.
object
Simplify: Configure code simplification.
object
Fix comments: Configure the Fix comments finishing touch for one-off review repairs.Learn more: Fix comments: apply CodeRabbit code fixes to pull requests
object
Fix Failing CI: Configure the CI fixer.Learn more: Fix CI failures
object
Resolve Merge Conflicts: Configure the merge-conflict resolver.Learn more: Resolve Merge Conflicts
array of object
default:[]
Custom Recipes: Define custom finishing touch recipes up to your plan limit. Trigger a recipe with
@coderabbitai run <recipe name>.Learn more: Custom Finishing Touch recipesPre-Merge Checks
reviews.pre_merge_checks
Learn more: Built-in Pre-Merge Checks
boolean
default:false
Override Requested Reviewers Only: When enabled, the pull request author cannot override/ignore failing pre-merge checks. Eligible actors are individually requested reviewers and, on GitHub, members of requested reviewer teams or submitted reviewers whose author association is OWNER, MEMBER, or COLLABORATOR.
object
Docstring Coverage: Check that docstring coverage meets the configured threshold.
object
Title Check: Validate the PR title against the requirements.
object
Description Check: Check that the PR description follows best practices.
object
Linked Issue Assessment: Assess how well the PR addresses linked issues.
array of object
default:[]
Custom Pre-merge Checks: Define custom checks that must pass before merging. Each check needs a unique name (≤50 chars) and deterministic instructions (≤10,000 chars).Learn more: Custom checks
.coderabbit.yaml
Tools
reviews.tools
Tools that provide additional context to code reviews.
Learn more: Third-party tools overview
object
ast-grep is a code analysis tool that helps you to find patterns in your codebase using abstract syntax trees patterns.Version:
v0.45.3object
ShellCheck is a static analysis tool that finds bugs in your shell scripts.Version:
v0.11.0object
Ruff is a Python linter and code formatter.Version:
v0.16.9object
markdownlint-cli2 is a static analysis tool to enforce standards and consistency for Markdown files.Version:
v0.23.3object
GitHub Checks integration configuration.
object
LanguageTool is a style and grammar checker for 30+ languages.
object
Biome is a fast formatter, linter, and analyzer for web projects.Version:
v2.5.14object
Hadolint is a Dockerfile linter.Version:
v2.15.1object
SwiftLint integration configuration object.Version:
v0.65.1object
PHPStan is a tool to analyze PHP code.Version:
v2.2.16object
PHPMD is a tool to find potential problems in PHP code.Version:
v2.15.0object
PHP CodeSniffer is a PHP linter and coding standard checker.Version:
v3.13.6object
golangci-lint is a fast linters runner for Go.Version:
v2.14.0object
YAMLlint is a linter for YAML files.Version:
v1.37.1object
Betterleaks is a secret scanner (an improved version of Gitleaks).Version:
v1.9.0object
TruffleHog is a secret scanner with verification capabilities that can detect and verify secrets in code.Version:
v3.96.0object
Checkov is a static code analysis tool for infrastructure-as-code files.Version:
v3.3.20object
TFLint is a Terraform linter for finding potential errors and enforcing best practices.Version:
v0.64.0object
Detekt is a static code analysis tool for Kotlin files.Version:
v1.23.8object
ESLint is a static code analysis tool for JavaScript files.
object
Flake8 is a Python linter that wraps PyFlakes, pycodestyle and Ned Batchelder’s McCabe script.Version:
v7.4.1object
Configuration for Infer to find bugs in Java and C/C++ codeVersion:
v1.3.0object
Fortitude is a Fortran linter that checks for code quality and style issues.Version:
v0.9.2object
RuboCop is a Ruby static code analyzer (a.k.a. linter) and code formatter.Version:
v1.91.0object
Buf offers linting for Protobuf files.Version:
v1.73.0object
Regal is a linter and language server for Rego.Version:
v0.43.0object
actionlint is a static checker for GitHub Actions workflow files.Version:
v1.7.12object
zizmor is a static security analyzer for GitHub Actions workflow files.Version:
v1.30.1object
PMD is an extensible multilanguage static code analyzer. It’s mainly concerned with Java.Version:
v7.28.0object
Configuration for Clang to perform static analysis on C and C++ codeVersion:
v14.0.6object
Cppcheck is a static code analysis tool for the C and C++ programming languages.Version:
v2.22.0object
Vale lints prose using the repository’s checked-in style rules.Version:
v3.23.0object
Verilator statically analyzes Verilog and SystemVerilog source files.Version:
v5.052object
OpenGrep is a high-performance static code analysis engine, compatible with Semgrep configurations.Version:
v1.30.1object
Semgrep is a static analysis tool designed to scan code for security vulnerabilities and code quality issues.Version:
v1.179.0object
CircleCI tool is a static checker for CircleCI config files.Version:
v1.0.51648object
Clippy is a collection of lints to catch common mistakes and improve your Rust code.
object
SQLFluff is an open source, dialect-flexible and configurable SQL linter.Version:
v4.3.0object
Configuration for Squawk to lint Postgres migrations and SQL for safe schema changesVersion:
v2.66.0object
Trivy is a comprehensive security scanner that detects misconfigurations and secrets in Infrastructure as Code filesVersion:
v0.74.0object
Configuration for Prisma Schema linting to ensure schema file qualityVersion:
v0.13.1object
Pylint is a Python static code analysis tool.Version:
v4.1.1object
Oxlint is a JavaScript/TypeScript linter for OXC written in Rust.Version:
v1.86.0object
Configuration for Shopify Theme Check to ensure theme quality and best practicesVersion:
cli 4.8.3, theme 3.58.2object
Configuration for Lua code linting to ensure code qualityVersion:
v1.2.0object
Brakeman is a static analysis security vulnerability scanner for Ruby on Rails applications.Version:
v8.0.6object
dotenv-linter is a tool for checking and fixing .env files for problems and best practicesVersion:
v4.0.0object
HTMLHint is a static code analysis tool for HTML files.Version:
v1.9.2object
Stylelint is a linter for stylesheets (CSS, SCSS, Sass, Less, SugarSS, Stylus) that helps avoid errors and enforce conventions.Version:
v17.14.0object
checkmake is a linter for Makefiles.Version:
v0.3.2object
OSV Scanner is a tool for vulnerability package scanning.Version:
v2.6.0object
oasdiff detects breaking changes between OpenAPI specifications.Version:
v1.32.1object
React Doctor scans React codebases for security, performance, correctness, and accessibility issues.Version:
v0.9.14object
Microsoft Presidio Analyzer 2.2.364 detects sensitive identifiers (including payment cards, US SSN, cryptocurrency wallets, and phone numbers) in changed files. Tune entities, thresholds, and languages in repository Presidio configuration (for example .presidiocli or AnalyzerEngineProvider YAML); the built-in scan uses fixed defaults and is skipped when that configuration is present.Version:
v2.2.364object
Blinter is a linter for Windows batch files that provides comprehensive static analysis to identify syntax errors, security vulnerabilities, performance issues, and style problems.Version:
v1.1.31object
smarty-lint is a linter for Smarty 3 template files that checks for common issues such as incorrect operator usage, naming conventions, empty blocks, and unquoted strings.Version:
v0.3.3object
ember-template-lint is a linter for Handlebars template files that checks for common issues such as accessibility violations, deprecated patterns, and template anti-patterns.Version:
v7.9.3object
SkillSpector is a security scanner for AI agent skills that detects vulnerabilities, malicious patterns, and security risksVersion:
v2.12.0object
PSScriptAnalyzer is a static code checker for PowerShell scripts and modules.Version:
v1.25.0Chat
boolean
default:true
Generate art in chat responses (ASCII or emoji).
boolean
default:true
Allow non-organization members to interact with CodeRabbit in comment chat. Set to false to restrict issue/review comment interactions to organization members on GitHub organization repositories. This does not affect automatic PR review eligibility.
boolean
default:true
Let CodeRabbit reply automatically without requiring a mention/tag.
Integrations
chat.integrations
object
Learn more: Jira Integration
object
Learn more: Linear Integration
Knowledge base
boolean
default:false
Opt Out: Disable knowledge base features that require data retention. Opting out removes any existing stored knowledge base data.Learn more: Knowledge Base overview
enum
default:"disabled"
Automatic Linking Mode: For Auto, private repositories may automatically link to public or private repositories, while public repositories may automatically link only to public repositories. Enabled uses context from any eligible repository in the organization, whether public or private. Disabled creates no automatic repository links. Manual repository links configured below are unaffected.One of the following:
auto, enabled, disabledLearn more: Multi-Repo Analysisboolean
default:false
Automatic Repository Linking: Deprecated. This setting has no effect. Use knowledge_base.automatic_linking_mode instead.Learn more: Multi-Repo Analysis
array of object
default:[]
Linked Repositories: Repositories that CodeRabbit should consider when reviewing PRs in this repo. Use this to surface cross-repo dependencies and catch breaking changes across related codebases.Learn more: Multi-Repo Analysis
Web search
knowledge_base.web_search
Learn more: Web Search
boolean
default:true
Web Search: Use web search to gather additional context.
Code guidelines
knowledge_base.code_guidelines
Use your coding guideline documents (see File Patterns) as review criteria.
Learn more: Code Guidelines
boolean
default:true
Enabled: Apply your organization’s coding standards during reviews.
array of object
default:[]
File Patterns: Additional guideline files, as glob strings or
{ files, applyTo } objects. A string entry such as **/CODING_STANDARDS.md locates guideline files. An object entry sets files (the guideline documents) and applyTo (the source files they govern, for example **/*.ts), each a comma-separated list of globs. Either form can name a file in another repository of your organization as repo:path or owner/repo:path (for example engineering-standards:frontend/react.md), read from that repository’s default branch. Supplements the default patterns; does not replace them. File names are case-sensitive.Learnings
knowledge_base.learnings
Learn more: Learnings
enum
default:"auto"
Learnings: Choose scope: ‘local’ (repo), ‘global’ (org), or ‘auto’ (local for public repos, global for private repos).One of the following:
local, global, autoauto: When reviewing a public repository, uses only that repository’s learnings. When reviewing a private repository, uses all of your organization’s learnings.global: Uses all of your organization’s learnings in every review.local: Uses only the learnings of the repository being reviewed.
integer
default:0
Days admins have to approve or reject a learning before it is automatically applied. Must be an integer between 0 and 30. Set to 0 to apply learnings immediately without approval.
Min: 0, Max: 30
Issues
knowledge_base.issues
Learn more: Knowledge Base overview
enum
default:"auto"
Issues: Choose scope for GitHub/GitLab issues: ‘local’ (repo), ‘global’ (org), or ‘auto’ (local for public repos, global for private repos).One of the following:
local, global, autoJira
knowledge_base.jira
Learn more: Knowledge Base overview
enum
default:"auto"
Jira: Use Jira as a knowledge source. ‘auto’ disables the integration for public repositories.One of the following:
auto, enabled, disabledarray of string
default:[]
Jira Project Keys: Restrict Jira context to these projects.Learn more: Jira Integration
array of string
default:[]
Jira Excluded Project Keys: Never use these Jira projects as CodeRabbit context, regardless of repository allowlists. Managed at the workspace level as a security policy; exclusions always take precedence over any allowlist.Learn more: Jira Integration
Linear
knowledge_base.linear
Learn more: Knowledge Base overview
enum
default:"auto"
Linear: Use Linear as a knowledge source. ‘auto’ disables the integration for public repositories.One of the following:
auto, enabled, disabledarray of string
default:[]
Linear Team Keys: Restrict Linear context to these teams (e.g. ‘ENG’).Learn more: Linear Integration
Pull requests
knowledge_base.pull_requests
Learn more: Knowledge Base overview
enum
default:"auto"
PRs: Choose scope: ‘local’ (repo), ‘global’ (org), or ‘auto’ (local for public repos, global for private repos).One of the following:
local, global, autoMCP
knowledge_base.mcp
Learn more: MCP Servers
enum
default:"auto"
MCP: Use MCP servers as a knowledge source. ‘auto’ disables the integration for public repositories.One of the following:
auto, enabled, disabledauto: Uses MCP servers as a knowledge source on private repositories and skips them on public repositories.enabled: Uses MCP servers on all repositories, including public ones.disabled: Never uses MCP servers as a knowledge source.
array of string
Disabled MCP Servers: Specify MCP server labels to disable (case-insensitive). These servers will be excluded from reviews and knowledge base queries.
Code generation
Docstring Generation
code_generation.docstrings
Settings for generating docstrings.
Learn more: Generate docstrings
enum
default:"en-US"
Language for generated docstrings (ISO language code).One of the following:
de, de-DE, de-AT, de-CH, en, en-US, en-AU, en-GB, en-CA, en-NZ, en-ZA, es, es-AR, fr, fr-CA, fr-CH, fr-BE, nl, nl-BE, pt-AO, pt, pt-BR, pt-MZ, pt-PT, ar, ast-ES, ast, be-BY, be, br-FR, br, ca-ES, ca, ca-ES-valencia, ca-ES-balear, da-DK, da, de-DE-x-simple-language, el-GR, el, eo, fa, ga-IE, ga, gl-ES, gl, it, ja-JP, ja, km-KH, km, ko-KR, ko, pl-PL, pl, ro-RO, ro, ru-RU, ru, sk-SK, sk, sl-SI, sl, sv, ta-IN, ta, tl-PH, tl, tr, uk-UA, uk, zh-CN, zh, zh-TW, crh-UA, crh, cs-CZ, cs, nb, no, nl-NL, de-DE-x-simple-language-DE, es-ES, it-IT, fa-IR, sv-SE, de-LU, fr-FR, bg-BG, bg, he-IL, he, hi-IN, hi, vi-VN, vi, th-TH, th, bn-BD, bnarray of object
default:[]
Path Instructions: Add path-specific guidelines for docstring generation.Learn more: Generate docstrings
Unit Test Generation
code_generation.unit_tests
Settings for generating unit tests.
Learn more: Generate unit tests
array of object
default:[]
Path Instructions: Add path-specific guidelines for unit test generation.Learn more: Generate unit tests
Issue enrichment
Auto enrich
issue_enrichment.auto_enrich
Settings for automatic issue enrichment.
Learn more: Issue Enrichment
boolean
default:false
Automatic Issue Enrichment: Analyze and enrich issues with additional context (related code, potential solutions, complexity assessment).
Planning
issue_enrichment.planning
Settings for issue planning.
Learn more: Issue Planner
boolean
default:true
Issue Planning: Generate an implementation plan for issues (early preview).
object
Labeling
issue_enrichment.labeling
Settings for issue labeling.
Learn more: Issue Enrichment
array of object
default:[]
Labeling Instructions: Define issue labels to suggest and when to suggest them.
boolean
default:false
Automatically apply suggested labels to the issue. When enabled without labeling instructions, labels are auto-suggested based on similar issues.
Related resources
Review commands
Learn about @coderabbitai commands
Tools reference
Browse all supported linters and analyzers