From c8eb901a30b5d5fe2a6c0e9924e97b4bd3fab9fa Mon Sep 17 00:00:00 2001 From: Jason McIntosh Date: Wed, 30 Jul 2025 12:22:33 -0400 Subject: [PATCH 01/25] Simplify and clarify GitHub integration instructions (#442) --- docs/platforms/github-com.md | 124 +++++++++++++++++------------------ docs/platforms/platforms.md | 55 +++++++++------- 2 files changed, 91 insertions(+), 88 deletions(-) diff --git a/docs/platforms/github-com.md b/docs/platforms/github-com.md index 60d919d7..c318307d 100644 --- a/docs/platforms/github-com.md +++ b/docs/platforms/github-com.md @@ -1,116 +1,110 @@ --- -title: Integrating CodeRabbit with GitHub.com +title: Integrate with GitHub.com description: Learn how to integrate CodeRabbit and add to your GitHub workflow. sidebar_label: GitHub.com -sidebar_position: 1 --- This is a step-by-step guide to integrate CodeRabbit with your GitHub repositories. -> **CodeRabbit** is an AI code reviewer designed to ease the challenges of code review, supporting repository maintainers and teams. It reviews your PRs and provides concise summaries, identifies potential issues, and offers insights that might be missed during manual reviews. +For an overview of how CodeRabbit integrates with Git platforms, see +[Add CodeRabbit to your repository](/platforms). -## How CodeRabbit Works? +For a hands-on tutorial with CodeRabbit performing code reviews on a live +GitHub repository that you create, see [Quickstart](/getting-started/quickstart). -> CodeRabbit integrates with GitHub, automating the code review process from the moment a pull request is created. +## Before you begin -It preprocesses the PR content, builds context, leverages Large Language Models for analysis, and then post-processes the AI response before posting the review back to GitHub. This streamlined workflow ensures thorough AI-powered code reviews without manual intervention. +You need to have a GitHub account, and ownership-level permissions of at least one repository associated with that account. -![How CodeRabbit Works](/img/integrations/how-codeRabbit-works.png) +If you want to authorize CodeRabbit to write code reviews for a repository contained in a GitHub organization, then you need ownership-level permission with that organization, as well. -## Let's Integrate CodeRabbit with GitHub +## Authorize CodeRabbit with your GitHub account -### 1. Accessing CodeRabbit +Before you can use CodeRabbit with GitHub, you need to +authorize CodeRabbit with your GitHub account. To do this, follow these steps: -Visit the [CodeRabbit login](https://app.coderabbit.ai/login?free-trial) page. You'll see all the authentication options, select "**Login with GitHub**" to proceed. +1. Visit [the CodeRabbit login page](https://app.coderabbit.ai/login). -![CodeRabbit Login](/img/integrations/login-self-hosted-github.png) +1. Click **Login with GitHub**. Your browser navigates to GitHub.com. -### 2. Authorization +1. If GitHub prompts to sign in to your GitHub account before continuing, then enter your GitHub login credentials as you normally would. Otherwise, continue to the next step. -When you choose **Login with GitHub** in step1, you'll be prompted to authorize CodeRabbit. +1. GitHub displays a summary of the information that CodeRabbit needs in order to integrate with your + GitHub account. This includes read-only access to the following: -> This step grants the necessary permissions for CodeRabbit to interact with your repositories and pull requests. + - Organizations and teams that are associated with your GitHub account. + - Email addresses that are associated with your GitHub account. -![Authorization Login](/img/integrations/authorization-codeRabbit.png) + To allow CodeRabbit access to this information, click **Authorize coderabbitai**. -### 3. Selecting Your Organization +After you complete these steps, your browser navigates to the CodeRabbit web interface. -Upon Authorization, If you're part of multiple organizations, you'll have the opportunity to choose which one you want to associate with CodeRabbit. This ensures that you're setting up the tool for the correct team or project. +Now that you've integrated CodeRabbit with your GitHub account, you need to give CodeRabbit additional permissions to work with your code repositories. To do this, see the next section. -![How to Select Organization in CodeRabbit](/img/integrations/select-organization.png) +## Allow CodeRabbit to access your repositories -### 4. Exploring the CodeRabbit Dashboard +Even after you've integrated CodeRabbit with your GitHub account, you need to +separately grant CodeRabbit the permissions that it needs to post code reviews and +create pull requests in your repositories. -Upon successful authorization, you'll be logged into the CodeRabbit user interface. +You need to authorize CodeRabbit separately for each GitHub organization whose repositories you want it to work with. You can give CodeRabbit permission to +work with all of the repositories associated with a GitHub organization, or limit its access to a select list. -Here, you can add repositories and configure CodeRabbit config settings for each repository. +### Overview of required permissions -![CodeRabbit Dashboard](/img/integrations/codeRabbit-dashboard.png) +CodeRabbit requires the following permissions to work with your repositories: -:::tip -If you opt to authorize all repositories during setup, CodeRabbit will automatically include any new repositories you create on GitHub in the future. This saves you the hassle of manual additions down the line. -::: - -### 5. CodeRabbit Configuration - -You can configure CodeRabbit through a YAML file or using the [App's UI](https://app.coderabbit.ai/login?free-trial). +- Read-only access to actions, checks, discussions, members, and metadata. -You can tailor CodeRabbit's functionality using the `.coderabbit.yaml` file, which you place directly in your GitHub repository. This file mirrors the options available in the CodeRabbit user interface, with each setting in the YAML corresponding to a specific toggle in the UI. Configure CodeRabbit either through the coderabbit.yaml file or the interface, depending on your preference. +- Read-and-write access to code, commit statuses, issues, and pull requests. :::note - -If a `.coderabbit.yaml` file exists in your GitHub repository, it takes precedence over any UI settings. Choose either the YAML file or UI configuration - you don't need to use both. **Refer CodeRabbit YAML schema [here](https://storage.googleapis.com/coderabbit_public_assets/schema.v2.json)** - +CodeRabbit requests read and write access to your repository in order for its code review, issue management, and pull request generation features to work. CodeRabbit never stores your code. For more information, see [the CodeRabbit Trust Center](https://trust.coderabbit.ai). ::: -Once your `.coderabbit.yaml` file is prepared according to your needs, simply place it in your GitHub repository, and you're all set — CodeRabbit is now integrated. - -> When a pull request is created targeting the master branch, CodeRabbit automatically initiates its review process. It analyzes the changes and generates a summary and walkthrough of the modifications. The specific feedback and analysis provided by CodeRabbit are determined by the options you've configured in your YAML file. - -Let's see a few examples of CodeRabbit's review comments from a specific pull request in one of the projects. - -This particular PR involved in changing the language model from LLaMA 2 to LLaMA 3, for testing purposes. These examples will showcase how CodeRabbit analyzed and commented on this significant model switch. - -## Sample PR Review Workflow using CodeRabbit - -CodeRabbit automatically generates a PR summary highlighting key changes. - -![CodeRabbit Summary](/img/integrations/summary-by-codeRabbit.png) +### Grant required permissions -This image shows CodeRabbit's review status for another pull request. It highlights that **12 actionable comments** were generated, and the review also includes additional comments on specific files, demonstrating CodeRabbit's comprehensive analysis of the code changes. +To give CodeRabbit access to one or more of your repositories, follow these steps: -![Actionable Comments By CodeRabbit](/img/integrations/actionable-comments-by-coderabbit.png) +1. Visit [the CodeRabbit web interface](https://app.coderabbit.ai/settings/repositories). -You can also use [CodeRabbit commands](https://docs.coderabbit.ai/guides/commands/) to chat with the AI code Reviewer. +1. Make sure that the correct GitHub organization for the repository is displayed + at the top of the web interface. To change the organization, click **Change + Organization** and select a different organization from the list. -![CodeRabbit Commands](/img/integrations/full-review.png) + If the repositories that you want to add are associated directly with your GitHub account, and not a separate organization, then select your account name as the organization. -CodeRabbit could generate a **code sequence diagram** when you request a full review. + If the organization containing the repository doesn't appear in the list, then you might + need to refresh the list of organizations that CodeRabbit has associated with your + GitHub account. For more information, see [Add organizations](/getting-started/adding-organizations). -The sequence diagram illustrates the precise flow of interactions between the objects in the system. +1. Click the **Add Repositories** button. Your browser navigates to GitHub.com. -![CodeRabbit Sequence Diagram](/img/integrations/coderabbit-sequence-diagram.png) + If the selected organization has no repositories registered with CodeRabbit, then your browser displays a CodeRabbit permissions dialog for setting up a new integration. Proceed to the next step. -Also, check out the response when asked for what improvements can be done on the code level. + Otherwise, your browser displays a GitHub settings page for your organization's existing CodeRabbit integration. Scroll down to the section titled **Repository access**, and then proceed to the next step. -![Code Improvements Suggested by CodeRabbit](/img/integrations/improvements.png) +1. Select which repositories you'd like to allow CodeRabbit to write code reviews for. -In addition to providing reviews and summaries, **CodeRabbit** can also detect configuration issues. + To give CodeRabbit access to all repositories in the organization, select **All repositories**. This also automatically grants CodeRabbit access to all repositories added to the organization in the future. -> For example, I accidentally set up both CodeRabbit Pro (The process we've been discussing) and the open-source version (Refer to [different config process](https://github.com/coderabbitai/ai-pr-reviewer?tab=readme-ov-file#install-instructions)) in my repository at the same time. + To give CodeRabbit access to specific, limited list of repositories, select **Only select repositories**, and then choose repositories from the list. -CodeRabbit automatically detects and alerts you about configuration conflicts. + :::note + You can change this setting later. + ::: -![Configuration Issues by CodeRabbit](/img/integrations/configuration.png) +1. Click the button at the bottom of the form, which has one of the following labels, depending upon context: -CodeRabbit generates detailed statistics and test plans for each pull request. + - **Install & Authorize**, if this organization has no repositories integrated with CodeRabbit, and you are an owner of this organization. + - **Save**, if this organization already has repositories integrated with CodeRabbit -![Statistics by CodeRabbit](/img/integrations/statistics.png) +1. If you are integrating an organization with CodeRabbit for the first time, then your browser navigates back to the CodeRabbit web interface. -![Test Plan by CodeRabbit](/img/integrations/test-plan.png) + Otherwise, your browser remains on your GitHub settings page, and you can manually navigate [back to the CodeRabbit web interface](https://app.coderabbit.ai/settings/repositories). -> CodeRabbit also allows you to configure **custom review instructions** based on your organization's needs, in case you want it to follow specific guidelines beyond the standard review, to learn more on [adding custom review instructions](/guides/review-instructions) +## What's next -Whether you manage a popular repository or are working on a smaller project, whether it's hosted on **GitLab, GitHub, or self-hosted GitHub or GitLab**, CodeRabbit can help streamline your development process. This AI Code Review assistant is designed to save you time by automating code reviews and offering insightful feedback. +- [Set your repository preferences](/guides/repository-settings) -> Explore, Experiment, Discover how [CodeRabbit](https://docs.coderabbit.ai/) can streamline your code review process using AI. +- [Review pull requests](/guides/code-review-overview) diff --git a/docs/platforms/platforms.md b/docs/platforms/platforms.md index d4cb1748..67689490 100644 --- a/docs/platforms/platforms.md +++ b/docs/platforms/platforms.md @@ -1,35 +1,44 @@ --- -title: Integrate with Git platforms -description: Overview of CodeRabbit's supported Git platforms. +title: Add CodeRabbit to your repository +description: Conceptual overview of integrating CodeRabbit with your Git platform +sidebar_label: Overview --- -CodeRabbit supports various Git platforms to provide code review for your repositories. For the cloud-hosted Git platforms, you can [login][login] to CodeRabbit and add your repositories. The following platforms are supported: +This page presents an overview of integrating CodeRabbit with your Git platform. +For a conceptual overview of CodeRabbit, see [Introduction](/). -## GitHub +## Use CodeRabbit with Git platforms -| Host | Support | -| ------------------------ | ---------------------------------------- | -| GitHub.com | [Supported](github-com.md) | -| GitHub Enterprise Server | [Supported](github-enterprise-server.md) | +CodeRabbit integrates with the following Git platforms: -## GitLab +- [GitHub.com](/platforms/github-com) +- [GitHub Enterprise Server](/platforms/github-enterprise-server) +- [GitLab.com](/platforms/gitlab-com) +- [Self-managed GitLab](/platforms/self-hosted-gitlab) +- [Azure DevOps](/platforms/azure-devops) +- [BitBucket Cloud](/platforms/bitbucket-cloud) -| Host | Support | -| ------------------- | ---------------------------------- | -| GitLab.com | [Supported](gitlab-com.mdx) | -| GitLab Self Managed | [Supported](self-hosted-gitlab.md) | +The exact steps for each platform are outlined in the pages linked above. That said, integrating any +Git platform with CodeRabbit follows this general pattern: -## Azure DevOps +1. Log into CodeRabbit using your Git platform account. -| Host | Support | -| ------------ | ---------------------------- | -| Azure DevOps | [Supported](azure-devops.md) | +1. Add the organizations containing the repositories that you want CodeRabbit to work with. You generally need ownership-level permissions with these organizations. (Different Git platforms might call their organizations different + things, such as "groups" in GitLab and "workspaces" in BitBucket.) -## Bitbucket +1. Create a dedicated CodeRabbit service account on your Git platform, if needed. We handle + this step for you on some platforms, such as GitHub.com. -| Host | Support | -| -------------------- | ---------------------------------------- | -| Bitbucket Datacenter | [Supported](../self-hosted/bitbucket.md) | -| Bitbucket Cloud | [Supported](./bitbucket-cloud.md) | +1. Grant CodeRabbit the permissions that it needs to work with one or more + of the repositories that you have ownership-level access to. -[login]: https://app.coderabbit.ai/login?free-trial +After you finish integrating CodeRabbit with one or more repositories, you can [start using CodeRabbit immediately](/guides/code-review-overview) using its default configuration, which automatically reviews or summarizes new pull requests. You can also [customize CodeRabbit’s configuration](/guides/configuration-overview) to suit your team's needs. + +## What's next {#whats-next} + +- [Integrate CodeRabbit with GitHub.com](/platforms/github-com) +- [Integrate CodeRabbit with GitHub Enterprise Server](/platforms/github-enterprise-server) +- [Integrate CodeRabbit with GitLab.com](/platforms/gitlab-com) +- [Integrate CodeRabbit with Self-managed GitLab](/platforms/self-hosted-gitlab) +- [Integrate CodeRabbit with Azure DevOps](/platforms/azure-devops) +- [Integrate CodeRabbit with BitBucket Cloud](/platforms/bitbucket-cloud) From 4842c646ab778b496dcebf0da35b726a3f4a6535 Mon Sep 17 00:00:00 2001 From: Jason McIntosh Date: Wed, 30 Jul 2025 13:03:03 -0400 Subject: [PATCH 02/25] Add a Learnings overview page. (#454) --- docs/guides/configuration-overview.md | 10 +++ docs/guides/initial-configuration.md | 2 +- docs/guides/learnings.md | 124 ++++++++++++++++++++++++++ docs/integrations/knowledge-base.md | 8 +- sidebars.ts | 1 + 5 files changed, 138 insertions(+), 7 deletions(-) create mode 100644 docs/guides/learnings.md diff --git a/docs/guides/configuration-overview.md b/docs/guides/configuration-overview.md index b2c401f2..3e54ebbe 100644 --- a/docs/guides/configuration-overview.md +++ b/docs/guides/configuration-overview.md @@ -72,3 +72,13 @@ This means that configuration is not merged or inherited - the highest priority The [Initial configuration guide](/guides/initial-configuration) tours you through several settings that we recommend that you review after you set up CodeRabbit with your organization. + +## Learnings {#learnings} + +As a complement to the configuration methods listed above, CodeRabbit keeps an internal database with _learnings_ that it collects about your team's code review preferences, based on your interactions with the CodeRabbit bot over time. CodeRabbit learnings let you fine-tune the ways that CodeRabbit conducts its code reviews in ways that are highly specific to your repositories, and your team's coding styles. + +For more information, see [Teach CodeRabbit your review preferences](/guides/learnings). + +## What's next {#whats-next} + +- [Initial configuration guide](/guides/initial-configuration) diff --git a/docs/guides/initial-configuration.md b/docs/guides/initial-configuration.md index 826a7948..5cea2afd 100644 --- a/docs/guides/initial-configuration.md +++ b/docs/guides/initial-configuration.md @@ -57,7 +57,7 @@ For more information, see ### Configure learnings {#learnings} -CodeRabbit learns your team's review preferences by letting you [teach it your preferences in plain language during code reviews](/integrations/knowledge-base#learnings). CodeRabbit remembers these preferences, and applies them to subsequent code reviews in the same repository. +CodeRabbit learns your team's review preferences by letting you [teach it your preferences in plain language during code reviews](/guides/learnings). CodeRabbit remembers these preferences, and applies them to subsequent code reviews in the same repository. This setting lets you set the scope of which stored learnings that CodeRabbit should apply to its code reviews. For more information, see [Learnings](/reference/configuration#learnings) in the configuration reference. diff --git a/docs/guides/learnings.md b/docs/guides/learnings.md new file mode 100644 index 00000000..38477db6 --- /dev/null +++ b/docs/guides/learnings.md @@ -0,0 +1,124 @@ +--- +title: Teach CodeRabbit your review preferences +description: An overview of the CodeRabbit learnings feature. +--- + +This page describes how you can configure the code-review behavior of CodeRabbit using natural-language +chat. + +For a conceptual overview of CodeRabbit configuration methods, see [Configure CodeRabbit](/guides/configuration-overview). For more information about performing code reviews with CodeRabbit, see +[Review pull requests](/guides/code-review-overview). + +## About CodeRabbit learnings {#about} + +As your team works with CodeRabbit, it learns your team's code-review +preferences based on chat interactions, and adds these preferences +to an internal database that it associates with your Git platform organization. We call these internal records _learnings_. + +
+ +
+ +CodeRabbit learnings are flexible, natural-language statements about code-review preferences whose purpose can include the following: + +- Special instructions about reviewing particular files. +- Guidance for reviewing all of the files of one repository. +- Code-review preferences that CodeRabbit must apply across all of your organization's repositories. + +Every time CodeRabbit prepares to add a comment to a pull request or issue, it loads all of the learnings that it has collected about your organization's code review preferences. CodeRabbit applies these learnings as additional context or instructions for its comment. + +CodeRabbit learnings complement the more traditional configuration that you set for your organization and its repositories using the CodeRabbit web interface or [`.coderabbit.yaml` files](/getting-started/configure-coderabbit). Learnings give you a convenient way to quickly set or correct the behavior of CodeRabbit in ways that are highly specific to your team's coding style, or in ways that the CodeRabbit configuration options don't otherwise account for. + +You can review and edit your organization's CodeRabbit learnings at any time, as detailed later in this page. + +## Add learnings {#add} + +To add learnings to the database CodeRabbit keeps about your organization's preferences, communicate +your preferences directly to the appropriate CodeRabbit service account using natural language, in a comment attached to any pull request or issue. For more information about chatting with CodeRabbit using comments, see [CodeRabbit chat](/guides/agent_chat/). + +If CodeRabbit decides to create one or more learnings based on a comment, then it makes this explicit in its response to that comment by adding a collapsible section titled **Learnings Added** to its own response comment. + +### An example of adding a learning {#example} + +Imagine a scenario where CodeRabbit has reviewed a GitHub-based pull request from your team that adds a feature to an authentication middleware library. CodeRabbit has flagged a certain file as needing improvement, attaching this comment to the relevant lines in its review: + +> Consider using nested try-catch blocks here to handle different error scenarios more comprehensively. + +If this critique disagrees with your team's coding practices specific to try-catch blocks, then you can reply to this CodeRabbit using a comment of your own, addressed to the `@coderabbitai` service account on GitHub: + +> @coderabbitai Actually, we've found that nested try-catch blocks make our auth middleware harder to debug in production. We prefer early returns with specific error codes - it's cleaner and our monitoring tools can track them better. + +CodeRabbit considers your reply, and decides to make a learning out of it. It acknowledges this in another reply: + +> You're absolutely right about the debugging benefits. Early returns with specific error codes do provide better clarity and monitoring capabilities. I'll remember this preference for your authentication middleware. Thank you for the guidance! + +CodeRabbit also adds a **Learnings added** section to this comment, making explicit the fact that this chat has modified its future behavior with your team. + +CodeRabbit then creates a new learnings record for itself. Along with metadata such as the pull request number, filename, and GitHub user associated with the learning, CodeRabbit adds this self-instructive text to the new record: + +> In authentication middleware, prefer returning early with specific error codes rather than nested try-catch blocks. This improves readability and makes error tracking easier in production environments. + +### Best practices for new learnings {#best-practices} + +When communicating with CodeRabbit during an active code review, you can help make any resulting learnings more specific by replying directly to review comments that CodeRabbit has left on specific files, rather than leaving comments on the overall pull request. This gives CodeRabbit more context when considering feedback, allowing it to create more specific learnings. + +## View learnings {#view} + +To view the learnings that CodeRabbit has associated with your organization, +follow these steps: + +1. Visit [the CodeRabbit web interface](https://app.coderabbit.ai/settings/repositories). + +1. In the sidebar, click **Learnings**. + +This displays a paged list of all of the learnings associated with your organization, sorted by creation time, newest-first. To see more details about any learnings record, click its text. + +### Filter displayed learnings {#filter} + +Over time, the learnings that CodeRabbit gathers for your organization can become quite numerous. This can make manually browsing the full list difficult. The CodeRabbit web interface has search and filtering tools to help you find specific learnings, based on the topic of the learning text, or on other metadata. + +To filter the displayed learnings by topic or concept, enter that topic or concept into the **Similarity search** field, and set **Top K** to the number of results you want returned. Because this is a vector-based similarity search, the returned learnings don't necessarily contain the exact text of your search terms. + +For example, to see the top ten learnings that have to do with error reporting, enter `error reporting` into **Similarity search** and set **Top K** to `10`. + +To filter the displayed learnings by repository, user, or file path, click **+ Filters**, and select additional criteria. + +### Edit or delete learnings {#edit} + +If your account has the **Admin** [CodeRabbit role](/guides/roles) with your organization, then you can freely edit the text of any stored learning, or delete it outright. + +To edit or delete a learning, follow these steps: + +1. Click the **Action** menu on the learning record, which resembles three dots. + +1. Select **Edit** or **Delete**. + +## Configure learnings storage and application {#configure} + +CodeRabbit has several configuration options that modify the storage and application of learnings. + +### Opt out of learnings storage {#opt-out} + +CodeRabbit enables learnings by default. To disable learnings, modify one of the following configuration options: + +- To disable all CodeRabbit [knowledge base](/integrations/knowledge-base) features for your organization or repository, which includes learnings, enable [the _Opt out_ setting](/reference/configuration#opt-out). + +- To disable all CodeRabbit features that require long-term data retention about your organization's use of CodeRabbit—including learnings—disable [the _Data retention_ setting](/reference/configuration#data-retention). + +:::warning +Disabling data retention immediately and irrevocably deletes all learnings that CodeRabbit has associated with your organization. +::: + +### Specify the scope of applied learnings {#scope} + +[The Learnings configuration setting](/reference/configuration#learnings) lets you specify the _scope_ that CodeRabbit applies to all +of the learnings it has collected about your organization. You can set this option to one of the +following values: + +- **`auto`**: When reviewing a public repository, CodeRabbit applies only the learnings specific to that repository. When reviewing private repository, CodeRabbit applies all of your organization's learnings. This is the default setting. +- **`global`**: CodeRabbit applies all of your organization's learnings to all code reviews. +- **`local`**: CodeRabbit applies only learnings associated with code reviews' respective repositories. + +## What's next {#whats-next} + +- [Add review instructions](/guides/review-instructions) diff --git a/docs/integrations/knowledge-base.md b/docs/integrations/knowledge-base.md index 1da862e0..9cdedc80 100644 --- a/docs/integrations/knowledge-base.md +++ b/docs/integrations/knowledge-base.md @@ -1,5 +1,5 @@ --- -title: Apply your code review preferences +title: Knowledge base overview description: Learn about CodeRabbit's internal knowledge base and its integrations with external services. --- @@ -17,11 +17,7 @@ For example, you can add a comment in a PR to chat directly with CodeRabbit. `@c Or you can comment directly on some lines of code in the PR. `@coderabbitai do not complain about lack of error handling here, it is handled higher up the execution stack.` -:::tip Video Tutorial - -Watch our [video walkthrough on learnings](https://www.youtube.com/watch?v=Yu0cmmOYA-U) for more information. - -::: +For more information, see [Teach CodeRabbit your review preferences](/guides/learnings). ## Code Guidelines {#code_guidelines} diff --git a/sidebars.ts b/sidebars.ts index 25fded60..487a363b 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -85,6 +85,7 @@ const sidebars: SidebarsConfig = { "getting-started/configure-coderabbit", "guides/initial-configuration", "integrations/knowledge-base", + "guides/learnings", "guides/review-instructions", "tools/tools", "guides/roles", From 530bacbb3ad9bbd5b424798aef9d01faaaac96e3 Mon Sep 17 00:00:00 2001 From: Karan Singh Date: Wed, 30 Jul 2025 17:05:07 -0700 Subject: [PATCH 03/25] Add useful information about Group Access tokens (GitLab & Gitlab-Self-Hosted) (#480) --- docs/platforms/gitlab-com.mdx | 8 +++++++- docs/platforms/self-hosted-gitlab.md | 6 ++++++ 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/docs/platforms/gitlab-com.mdx b/docs/platforms/gitlab-com.mdx index c276cd35..30b23031 100644 --- a/docs/platforms/gitlab-com.mdx +++ b/docs/platforms/gitlab-com.mdx @@ -107,7 +107,13 @@ By default, GitLab restricts this option to users on the Premium or Ultimate tie 5. Ensure the following scopes are selected: `api`. 6. Ensure Developer Access is provided. ---- +:::tip + +Group Access Tokens create bot users with generic GitLab-generated usernames (like `group_63_bot_5753...`). If you prefer a more descriptive username for your CodeRabbit bot, you can customize it using the [GitLab API](https://docs.gitlab.com/api/users/#modify-a-user). + +You can find the bot's user ID through the CodeRabbit UI if connected, or by visiting the bot user's profile from your Group Members page in GitLab. + +::: ### Where to Provide CodeRabbit the Access Token diff --git a/docs/platforms/self-hosted-gitlab.md b/docs/platforms/self-hosted-gitlab.md index 3fa18a71..bd330887 100644 --- a/docs/platforms/self-hosted-gitlab.md +++ b/docs/platforms/self-hosted-gitlab.md @@ -71,6 +71,12 @@ After the user is created, you can retrieve the **User ID** from that user's profile and generate an [**access token**](#generating-personal-access-token). The access token is used to post reviews on merge requests. +:::note + +If you prefer, you can create a Group Access Token which will create a dedicated user on your behalf. For more information, see [Group Access Token](/docs/platforms/gitlab-com.mdx#group-access-token) + +::: + We recommend using the CodeRabbit [logo](/img/integrations/logo.png) as the profile picture to ensures easy recognition. #### **Creating OAuth2 application** From e3dd9218abccd868a83717579f0b0b8f81a056cb Mon Sep 17 00:00:00 2001 From: Lewis Mbae Date: Wed, 30 Jul 2025 17:10:06 -0700 Subject: [PATCH 04/25] Fix ordering of commands in self-hosted docs (#477) --- docs/self-hosted/bitbucket.md | 12 ++++++------ docs/self-hosted/gitlab.md | 12 ++++++------ 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/self-hosted/bitbucket.md b/docs/self-hosted/bitbucket.md index 92c539f8..9d20ec39 100644 --- a/docs/self-hosted/bitbucket.md +++ b/docs/self-hosted/bitbucket.md @@ -157,18 +157,18 @@ cat coderabbit.json | docker login -u _json_key --password-stdin us-docker.pkg.d docker pull us-docker.pkg.dev/coderabbitprod/self-hosted/coderabbit-agent:latest ``` -### Verify the image is up +## Host the image -You can query `/health` endpoint to verify that the `coderabbit-agent` service is up and running. +You can host the image on a server, serverless function, or container environment and expose port `8080`. Run the Docker image with the equivalent command on your chosen platform, ensuring you replace the `.env` file path with the path to your actual `.env` file: ```bash -curl 127.0.0.1:8080/health +docker run --env-file .env --publish 127.0.0.1:8080:8080 us-docker.pkg.dev/coderabbitprod/self-hosted/coderabbit-agent:latest ``` -## Host the image +### Verify the image is up -You can host the image on a server, serverless function, or container environment and expose port `8080`. Run the Docker image with the equivalent command on your chosen platform, ensuring you replace the `.env` file path with the path to your actual `.env` file: +You can query `/health` endpoint to verify that the `coderabbit-agent` service is up and running. ```bash -docker run --env-file .env --publish 127.0.0.1:8080:8080 us-docker.pkg.dev/coderabbitprod/self-hosted/coderabbit-agent:latest +curl 127.0.0.1:8080/health ``` diff --git a/docs/self-hosted/gitlab.md b/docs/self-hosted/gitlab.md index 26ad309d..1e8121cf 100644 --- a/docs/self-hosted/gitlab.md +++ b/docs/self-hosted/gitlab.md @@ -203,18 +203,18 @@ cat coderabbit.json | docker login -u _json_key --password-stdin us-docker.pkg.d docker pull /coderabbit-agent:latest ``` -### Verify the image is up +## Host the image -You can query `/health` endpoint to verify that the coderabbit-agent service is up and running. +You can host the image on a server, serverless function, or container environment and expose port `8080`. Run the Docker image with the equivalent command on your chosen platform, ensuring you replace the `.env` file path with the path to your actual `.env` file: ```bash -curl 127.0.0.1:8080/health +docker run --env-file .env --publish 127.0.0.1:8080:8080 /coderabbit-agent:latest ``` -## Host the image +### Verify the image is up -You can host the image on a server, serverless function, or container environment and expose port `8080`. Run the Docker image with the equivalent command on your chosen platform, ensuring you replace the `.env` file path with the path to your actual `.env` file: +You can query `/health` endpoint to verify that the coderabbit-agent service is up and running. ```bash -docker run --env-file .env --publish 127.0.0.1:8080:8080 /coderabbit-agent:latest +curl 127.0.0.1:8080/health ``` From ebe72ced2d7b4c3bc2966df10da25e9e1c0d4352 Mon Sep 17 00:00:00 2001 From: Kian-Meng Ang Date: Thu, 31 Jul 2025 08:32:09 +0800 Subject: [PATCH 05/25] Fix typos (#479) Found via `codespell -S pnpm-lock.yaml -L ned,sav,paket` --- docs/changelog.md | 2 +- docs/faq.md | 2 +- docs/guides/custom-reports.md | 6 +++--- docs/guides/ondemand-reports.md | 2 +- docs/guides/reports-overview.md | 2 +- docs/guides/setup-best-practices.md | 2 +- docs/reference/configuration.md | 12 ++++++------ tailwind.config.js | 2 +- 8 files changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/changelog.md b/docs/changelog.md index ec081fb5..2570a905 100644 --- a/docs/changelog.md +++ b/docs/changelog.md @@ -250,7 +250,7 @@ import ProPlanNotice from "@site/src/components/ProPlanNotice.mdx" New and Improved Dashboards to provide more useful feedback such as: -- Avgerage PR Merge Time +- Average PR Merge Time - Weekly Pull Request Activity - Number of PRs Reviewed - Acceptance rate of CodeRabbit Suggestions diff --git a/docs/faq.md b/docs/faq.md index 795ce900..f248b517 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -63,7 +63,7 @@ CodeRabbit works with all programming languages, with varying proficiency based - Available training data - Community usage patterns -### Whats the difference between CodeRabbit Code Reviews and CodeRabbit Reports? +### What's the difference between CodeRabbit Code Reviews and CodeRabbit Reports? CodeRabbit offers two distinct features that serve different roles in your development workflow: diff --git a/docs/guides/custom-reports.md b/docs/guides/custom-reports.md index b2a10504..6fcc1e77 100644 --- a/docs/guides/custom-reports.md +++ b/docs/guides/custom-reports.md @@ -103,7 +103,7 @@ Contained within the `` tag. #### Summarized PR Details - ``: string - Contains the body of your pull request (aka the PR description at the top of the PR page). -- ``: string - Contains a file by file summary of the changes made in the PR in markdown format. This summary is generated by CodeRabbit AI durring the PR review process. This includes several sections for each file that was changed: +- ``: string - Contains a file by file summary of the changes made in the PR in markdown format. This summary is generated by CodeRabbit AI during the PR review process. This includes several sections for each file that was changed: - `filename`: string - The name of the file that was changed. - `AI-generated summary of changes`: markdown - An overall summary of the changes made in the file. - `Alterations to the declarations of exported or public entities`: markdown - A more specific breakdown of the changes made to the file such as exactly what was added, removed, or modified. @@ -307,9 +307,9 @@ Issues and tickets brings in conversations, descriptions, and comments from Jira This option gives you the ability to create a report limited only to pull requests containing a "Score Card" or "Score Chart" bot comment from CodeRabbit or other bots. To enable issues and tickets you must include the tag `` in your prompt. -> **IMPORTANT:** This will automatically remove any pull requests from your reports if they do not contain a "Score Card" or "Score Chart" bot comment. Using this option without setting up a flow to create these comments will result in `No new pull request activity in the last XYZ hours` errors. Do not enable this option unless you have asked coderabbit to create a "Score Card" thourhg a comment or implimented the "Score Chart" bot comment flow below. +> **IMPORTANT:** This will automatically remove any pull requests from your reports if they do not contain a "Score Card" or "Score Chart" bot comment. Using this option without setting up a flow to create these comments will result in `No new pull request activity in the last XYZ hours` errors. Do not enable this option unless you have asked coderabbit to create a "Score Card" thourhg a comment or implemented the "Score Chart" bot comment flow below. -For example you can ask coderabbit to check serveral conditions on a pull request and produce a "Score Chart": +For example you can ask coderabbit to check several conditions on a pull request and produce a "Score Chart":
Click to view example User Score Card/Chart Comment: diff --git a/docs/guides/ondemand-reports.md b/docs/guides/ondemand-reports.md index af380164..49214e32 100644 --- a/docs/guides/ondemand-reports.md +++ b/docs/guides/ondemand-reports.md @@ -14,7 +14,7 @@ import ProPlanNotice from '@site/src/components/ProPlanNotice.mdx'; This page is about using the CodeRabbit API to generate on-demand reports about your organization's usage of CodeRabbit. For a conceptual overview of reports in CodeRabbit, see [Generate reports](/guides/reports-overview). -If you're new to CodeRabbit's reporting features, then we recommend starting with [Scheduled reports](/guides/scheduled-reports) to understand the available options and capabilities. In almost every scenario we recommend using the **Scheduled Reports** option. The **On-demand Report** does not have any additional benifits from the **Scheduled Reports** and has many limitations. +If you're new to CodeRabbit's reporting features, then we recommend starting with [Scheduled reports](/guides/scheduled-reports) to understand the available options and capabilities. In almost every scenario we recommend using the **Scheduled Reports** option. The **On-demand Report** does not have any additional benefits from the **Scheduled Reports** and has many limitations. ## API Access diff --git a/docs/guides/reports-overview.md b/docs/guides/reports-overview.md index b15329f0..5095364f 100644 --- a/docs/guides/reports-overview.md +++ b/docs/guides/reports-overview.md @@ -26,7 +26,7 @@ There are two ways to generate reports: - **[On-demand Reports](/guides/ondemand-reports)**: If you want to test a report format and produce a single report once, try the "On-demand Reports" Option. You can also generate reports programmatically through our API, but we do not recommend this as the API reporting is in beta. If you want to run an **On-demand Report** more than once then you must use the **Scheduled Reports** option. -In almost every scenario we recommend using the **Scheduled Reports** option. The **On-demand Report** does not have any additional benifits from the **Scheduled Reports** and has many limitations. +In almost every scenario we recommend using the **Scheduled Reports** option. The **On-demand Report** does not have any additional benefits from the **Scheduled Reports** and has many limitations. ## Customize reports using natural language {#customize} diff --git a/docs/guides/setup-best-practices.md b/docs/guides/setup-best-practices.md index c6caa094..0533da5e 100644 --- a/docs/guides/setup-best-practices.md +++ b/docs/guides/setup-best-practices.md @@ -1,6 +1,6 @@ --- title: "Setup and configuration best practices" -description: Best practices for seting up CodeRabbit. +description: Best practices for setting up CodeRabbit. sidebar_label: Setup and configuration --- diff --git a/docs/reference/configuration.md b/docs/reference/configuration.md index 5b59933f..00e71f6d 100644 --- a/docs/reference/configuration.md +++ b/docs/reference/configuration.md @@ -604,8 +604,8 @@ Set the commit status to 'pending' when the review is in progress and 'success' Activate this setting to disallow CodeRabbit from caching your repository's code and dependencies. This forces CodeRabbit to download the code and dependencies fresh from the repository for every code review that it performs. When caching is allowed, then CodeRabbit stores a cache of code and metadata from -your repostory for up to seven days after its most recent code review. This cache -lets CodeRabbit save time and effort in between subsquent reviews of the same +your repository for up to seven days after its most recent code review. This cache +lets CodeRabbit save time and effort in between subsequent reviews of the same repository. For more information, see [Caching](/reference/caching/). We recommend leaving this setting off, which allows caching, and can speed up @@ -902,10 +902,10 @@ For more information, see [Speed up reviews by adding path filters](https://docs -Path instructions are additional sets of instructions, expressed in natural lanaguge, -that you provide to CodeRabbit for reveiwing certain files in your repository. +Path instructions are additional sets of instructions, expressed in natural language, +that you provide to CodeRabbit for reviewing certain files in your repository. -You associate each set of instuctions with a file path relative to the root +You associate each set of instructions with a file path relative to the root of your repository. Your path specification can use extended glob patterns. The following example defines a set of path instructions for all TypeScript @@ -929,7 +929,7 @@ path_instructions: -For further examples of path instructions specific to various programming langauges, +For further examples of path instructions specific to various programming languages, see [the `awesome-coderabbit` public repository](https://github.com/coderabbitai/awesome-coderabbit/tree/main/configs). #### Poem diff --git a/tailwind.config.js b/tailwind.config.js index b24582d0..dd081f63 100644 --- a/tailwind.config.js +++ b/tailwind.config.js @@ -21,7 +21,7 @@ module.exports = { preflight: false, // disable Tailwind's reset }, content: ["./src/**/*.{js,jsx,ts,tsx}", "../docs/**/*.mdx"], // my markdown stuff is in ../docs, not /src - darkMode: ["class", '[data-theme="dark"]'], // hooks into docusaurus' dark mode settigns + darkMode: ["class", '[data-theme="dark"]'], // hooks into docusaurus' dark mode settings theme: { fontFamily: { figtree: ["Figtree", "sans-serif"], From 981b7e0421e483fac715c0d90d3b7b180126c3eb Mon Sep 17 00:00:00 2001 From: Karan Singh Date: Wed, 30 Jul 2025 23:37:31 -0700 Subject: [PATCH 06/25] Misc typos (#481) --- docs/guides/custom-reports.md | 6 +++--- docs/reference/configuration.md | 8 ++++---- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/guides/custom-reports.md b/docs/guides/custom-reports.md index 6fcc1e77..48d37a74 100644 --- a/docs/guides/custom-reports.md +++ b/docs/guides/custom-reports.md @@ -307,9 +307,9 @@ Issues and tickets brings in conversations, descriptions, and comments from Jira This option gives you the ability to create a report limited only to pull requests containing a "Score Card" or "Score Chart" bot comment from CodeRabbit or other bots. To enable issues and tickets you must include the tag `` in your prompt. -> **IMPORTANT:** This will automatically remove any pull requests from your reports if they do not contain a "Score Card" or "Score Chart" bot comment. Using this option without setting up a flow to create these comments will result in `No new pull request activity in the last XYZ hours` errors. Do not enable this option unless you have asked coderabbit to create a "Score Card" thourhg a comment or implemented the "Score Chart" bot comment flow below. +> **IMPORTANT:** This will automatically remove any pull requests from your reports if they do not contain a "Score Card" or "Score Chart" bot comment. Using this option without setting up a flow to create these comments will result in `No new pull request activity in the last XYZ hours` errors. Do not enable this option unless you have asked CodeRabbit to create a "Score Card" through a comment or implemented the "Score Chart" bot comment flow below. -For example you can ask coderabbit to check several conditions on a pull request and produce a "Score Chart": +For example, you can ask CodeRabbit to check several conditions on a pull request and produce a "Score Chart":
Click to view example User Score Card/Chart Comment: @@ -461,7 +461,7 @@ You will create a new chart averaging all the values from various pull requests - Only include checks for very specific scenarios, such as a specific check failing or using tabs vs spaces. - Do not use general rules without explaining specifically what they mean. If you add "Insure the pull request follows development best practices" you must define what "development best practices" actually mean or the AI will guess. - Make one point for each specific check and make sure its a True/False condition. -- Instead of manually commenting on pull requests you can use the [Github Actions Bot](https://github.com/marketplace/actions/create-or-update-comment) to automatically comment on pull requests and trigger coderabbit score card/chart comments by including `@coderabbit` in the comment. +- Instead of manually commenting on pull requests, you can use the [GitHub Actions Bot](https://github.com/marketplace/actions/create-or-update-comment) to automatically comment on pull requests and trigger CodeRabbit score card/chart comments by including `@coderabbitai` in the comment. ## Best Practices diff --git a/docs/reference/configuration.md b/docs/reference/configuration.md index 00e71f6d..92a33b6d 100644 --- a/docs/reference/configuration.md +++ b/docs/reference/configuration.md @@ -301,11 +301,11 @@ If enabled, then the reviews that CodeRabbit generates include assessments of ho Besides this setting, issue assessment requires at least one of the following: -- You use the built-in issue managemet system of GitHub or GitLab. +- You use the built-in issue management system of GitHub or GitLab. - You have integrated CodeRabbit with an external issue manager. For more information, see [Integrate issue tracking](/integrations/issue-integrations/) -and [Let CodeRabbit read your issue trakcer](https://docs.coderabbit.ai/guides/setup-best-practices#issues). +and [Let CodeRabbit read your issue tracker](https://docs.coderabbit.ai/guides/setup-best-practices#issues). #### Auto Apply Labels @@ -909,7 +909,7 @@ You associate each set of instructions with a file path relative to the root of your repository. Your path specification can use extended glob patterns. The following example defines a set of path instructions for all TypeScript -and JavaScript files in a reposistory's `src` directory: +and JavaScript files in a repository's `src` directory: @@ -1398,7 +1398,7 @@ We recommend leaving this option enabled. A list of branches that CodeRabbit performs automatic code reviews on, other -than the reposiorty's main branch (usually `main` or `master`.) +than the repository's main branch (usually `main` or `master`.) For example, if you add `staging` as a base branch, then CodeRabbit automatically reviews pull requests on both your repository's default branch and its `staging` branch. From 12f8e51ee1c361303792d1867bc1ff747e0e02e4 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 31 Jul 2025 20:40:50 +0000 Subject: [PATCH 07/25] Update schema.v2.json --- static/schema/schema.v2.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index a84d875a..b31867ae 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -327,7 +327,7 @@ "type": "string" }, "default": [], - "description": "Restrict automatic reviews to only those pull requests that match one of the specified labels." + "description": "List of labels to control which PRs/MRs to review. Labels starting with '!' are negative matches. Examples: ['bug', 'feature'] - reviews PRs with 'bug' OR 'feature' label. ['!wip'] - reviews all PRs except those with 'wip' label. ['bug', '!wip'] - reviews PRs with 'bug' label but not if they have 'wip' label." }, "drafts": { "type": "boolean", From 3a81b58380e8b13f1218fdcf5c04fc70412c51b5 Mon Sep 17 00:00:00 2001 From: Sahil Date: Thu, 31 Jul 2025 14:17:12 -0700 Subject: [PATCH 08/25] Update configuration.md (#484) Fixing a missed | to denote that path instructions must be an array of strings --- docs/reference/configuration.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/reference/configuration.md b/docs/reference/configuration.md index 92a33b6d..eb070e23 100644 --- a/docs/reference/configuration.md +++ b/docs/reference/configuration.md @@ -919,12 +919,12 @@ and JavaScript files in a repository's `src` directory: ```yaml path_instructions: - path: src/**/*.{ts,tsx,js} - instructions: - - Review the React.js/TypeScript/JavaScript code for best practices - - Check for common security vulnerabilities such as: - - SQL Injection - - Insecure dependencies - - Sensitive data exposure + instructions: | + - Review the React.js/TypeScript/JavaScript code for best practices + - Check for common security vulnerabilities such as: + - SQL Injection + - Insecure dependencies + - Sensitive data exposure ``` From 1d1d0f5ec6d94a4d0d6143b21f8aab16e048761e Mon Sep 17 00:00:00 2001 From: Tom Elizaga Date: Mon, 4 Aug 2025 21:20:21 -0700 Subject: [PATCH 09/25] Update changelog to include dark theme and MCP (#486) * Update changelog to include August 1, 2025 entry for Dark Theme Support in UI App * Update changelog to include August 4, 2025 entry for Model Context Protocol (MCP) Server Integration - Early Access --- docs/changelog.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/changelog.md b/docs/changelog.md index 2570a905..21d85d40 100644 --- a/docs/changelog.md +++ b/docs/changelog.md @@ -5,6 +5,18 @@ description: The latest updates and changes to CodeRabbit. sidebar_position: 13 --- +## August 4, 2025 + +### Model Context Protocol (MCP) Server Integration - Early Access + +Pro users can now connect CodeRabbit to your external tools and knowledge bases to provide more contextual code reviews. Our AI automatically pulls relevant information from your documentation, project management tools, and internal wikis to better understand your code changes and business requirements. Connect your custom MCP servers through Settings > Integrations to get reviews and chat conversations that understand your full development context. + +## August 1, 2025 + +### Dark Theme Support for UI App + +CodeRabbit app now supports Light, Dark, and System themes. Use the new theme toggle next to your profile to switch modes. + ## July 23, 2025 ### ⚡️ Unit Test Generation - Beta From ee5a787fde59b4f196bd268a14d4af54cb706dfe Mon Sep 17 00:00:00 2001 From: Jason McIntosh Date: Tue, 5 Aug 2025 15:50:53 -0400 Subject: [PATCH 10/25] Add a new reference section for code guidelines. (#483) --- docs/integrations/knowledge-base.md | 29 +++++---- docs/reference/configuration.md | 94 +++++++++++++++++++++++++++++ 2 files changed, 110 insertions(+), 13 deletions(-) diff --git a/docs/integrations/knowledge-base.md b/docs/integrations/knowledge-base.md index 9cdedc80..24b2d1be 100644 --- a/docs/integrations/knowledge-base.md +++ b/docs/integrations/knowledge-base.md @@ -19,20 +19,23 @@ Or you can comment directly on some lines of code in the PR. `@coderabbitai do n For more information, see [Teach CodeRabbit your review preferences](/guides/learnings). -## Code Guidelines {#code_guidelines} +## Code Guidelines {#code-guidelines} -CodeRabbit will analyse and learn from your organisation's code guidelines, which you can set up in the knowledge base section. These guidelines will then be used to conduct thorough code reviews. +CodeRabbit can read _code guideline_ files that set standards and expectations about +your team's coding practices, described in natural language. CodeRabbit applies any instructions it reads from a repository's code guideline files to all subsequent code reviews. -The following patterns are scanned by default. +By default, CodeRabbit looks for and loads guideline files used by other AI coding assistants, including the following: -```text -**/.cursorrules -.github/copilot-instructions.md -**/CLAUDE.md -**/.cursor/rules/* -**/.windsurfrules -**/.clinerules/* -**/.rules/* -``` +- Claude Code +- Cursor +- Gemini +- GitHub Copilot +- Windsurf -![Illustration of code guidelines configuration](/img/knowledge-base/code-guidelines.png) +You can also mark any other file +or set of files in your repository as code guidelines by providing CodeRabbit with a list +of paths to those files. + +This feature is enabled by default; you can disable it if needed. + +For more information about configuring the code guidelines feature, see [Code guidelines](/reference/configuration#code-guidelines) in the configuration reference page. diff --git a/docs/reference/configuration.md b/docs/reference/configuration.md index eb070e23..d95fbaa0 100644 --- a/docs/reference/configuration.md +++ b/docs/reference/configuration.md @@ -1976,6 +1976,100 @@ Specify the Jira project keys to use for the knowledge base. Specify the scope of learnings to use for the knowledge base. 'local' uses the repository's learnings, 'global' uses the organization's learnings, and 'auto' uses repository's learnings for public repositories and organization's learnings for private repositories. +### Code guidelines + +You can define a list of paths that guide CodeRabbit to your organization's code guidelines. +If you do, then CodeRabbit applies these guidelines to its code reviews. For more +information, see [Code Guidelines](/integrations/knowledge-base#code_guidelines). + +#### Enable code guidelines + + + + + + + + + + + + + +
LocationKnowledge Base > Enabled
Defaulttrue
+ + + + + + + + + + + + + + + + +
Field`knowledge_base.code_guidelines.enabled`
Datatypeboolean
Default`true`
+ + + +Enable CodeRabbit to enforce your organization's coding standards during reviews. + +#### File patterns + + + + + + + + + + + + + +
LocationKnowledge Base > File Patterns
Default_No patterns_
+ + + + + + + + + + + + + + + + +
Field`knowledge_base.code_guidelines.filePatterns`
Datatypearray
Default`[]`
+ + + +A list of path specifications to your repository's coding guideline documents, relative +to the root of your repository. Fileglob matching is allowed. Paths are case-sensitive. + +If the code guidelines feature is enabled, then CodeRabbit applies code-guideline +documents found at the following paths, in addition to any paths that you define: + +- `**/.cursorrules` +- `.github/copilot-instructions.md` +- `**/CLAUDE.md` +- `**/GEMINI.md` +- `**/.cursor/rules/*` +- `**/.windsurfrules` +- `**/.clinerules/*` +- `**/.rules/*` +- `**/AGENT.md` + ### Linear #### Enable Linear From cce50ca413a8a11aee95c71fb9e4c2ff28049e63 Mon Sep 17 00:00:00 2001 From: Tomasz Hanc <7013293+tomaszhanc@users.noreply.github.com> Date: Thu, 7 Aug 2025 19:16:28 +0200 Subject: [PATCH 11/25] Add estimate_code_review_effort to yaml-template.md (#488) --- docs/reference/yaml-template.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/reference/yaml-template.md b/docs/reference/yaml-template.md index 9fac39e2..99fafa34 100644 --- a/docs/reference/yaml-template.md +++ b/docs/reference/yaml-template.md @@ -31,6 +31,7 @@ reviews: collapse_walkthrough: false changed_files_summary: true sequence_diagrams: true + estimate_code_review_effort: true assess_linked_issues: true related_issues: true related_prs: true From e34339bde68fa68f2e31f92ef9f1a081670930e6 Mon Sep 17 00:00:00 2001 From: Edgar Cerecerez Date: Thu, 7 Aug 2025 22:58:14 -0600 Subject: [PATCH 12/25] Updating bitbucket integration docs to account for on-prem (#476) * Updating bitbucket integration docs to account for on-prem Removed references to Bitbucket Cloud and left the more ambiguous Bitbucket to account for both on prem and cloud. * Update bitbucket-cloud.md * Delete future-development.md --- docs/future-development.md | 58 ------------------------------- docs/platforms/bitbucket-cloud.md | 6 ++-- 2 files changed, 3 insertions(+), 61 deletions(-) delete mode 100644 docs/future-development.md diff --git a/docs/future-development.md b/docs/future-development.md deleted file mode 100644 index e3c7c4d6..00000000 --- a/docs/future-development.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: CodeRabbit Features -sidebar_label: Future Development -description: Learn how CodeRabbit works in a pull request review. -sidebar_position: 12 ---- - -# Future Development - -We are actively iterating and refining CodeRabbit, and this is a sneak peek into the upcoming milestones and releases. We are focused on making the Applied AI review better than the median manual review. In addition to that, we are looking at a holistic user experience with various integrations and types of reviews. - -## Applied AI Improvements - -We are actively trying to make the application of Generative AI more useful, relevant, meaningful for the coder and reviewer journey. Our immediate focus is - -### Accuracy and Conciseness Enhancements - -- Refining knowledge base context understanding -- Implementing advanced summarization techniques -- Implementing a knowledge base feature library - -### Learning Refinements - -- We have made significant improvement of the learning Enhancing reinforcement learning based on the user feedback - -## New Feature Enhancements - -### Expanded Integrations - -We are integrating various tool chains to enable coders and reviewers to have a consistent experience irrespective of the tools. The immediate tools would be: - -- **Circle CI** -- **Jenkins** - -### Communication Tool Integrations - -Communication and the user experience of review via various communication tools will be key. We will start with integrations to Slack and Microsoft Teams and will be diving into the design engineering of these flows further: - -- **Slack**: Real-time notifications and interactive discussions -- **Microsoft Teams**: Code review conversations within the Microsoft ecosystem - -### Enhanced Review Capabilities - -These are additional capabilities that can also be reviewed in the same PR to accelerate the coder and reviewer journey. This includes pipeline failure analysis and resolution, as well as vulnerability assessment. - -#### Pipeline Failure Analysis - -- Automated analysis of CI/CD pipeline failures -- AI-driven suggestions for resolving issues -- Historical tracking of pipeline performance - -### Finishing Touches - -Finishing touches are about experience that often take developers time away from what they like doing best coding. But adding finishing touches is crucial and should follow the ontology and taxonomy. We will start by looking into specific areas such as documentation of code as an example. - -> Disclaimer: any product roadmap features mentioned below are only meant to outline -> our general product direction. This documentation is for informational purposes -> only and may not be incorporated into any contract. diff --git a/docs/platforms/bitbucket-cloud.md b/docs/platforms/bitbucket-cloud.md index 385d46ed..a708441b 100644 --- a/docs/platforms/bitbucket-cloud.md +++ b/docs/platforms/bitbucket-cloud.md @@ -1,17 +1,17 @@ --- title: "Bitbucket Cloud" description: "Learn how to integrate CodeRabbit with Bitbucket Cloud." -sidebar_label: "Bitbucket Cloud" +sidebar_label: "Bitbucket" sidebar_position: 6 --- -CodeRabbit integrates with Bitbucket Cloud to enhance code review and collaboration by: +CodeRabbit integrates with Bitbucket to enhance code review and collaboration by: - Automatically initiating code reviews for newly created merge requests. - Displaying review comments and suggestions directly on merge requests. - Enabling seamless interaction with the CodeRabbit bot for real-time feedback and assistance. -This guide will assist you in effectively integrating CodeRabbit with Bitbucket Cloud. +This guide will assist you in effectively integrating CodeRabbit with Bitbucket Cloud. [Click here](https://docs.coderabbit.ai/self-hosted/bitbucket) for instructions integrating Bitbucket Data Center with CodeRabit self-hosted edition. ## Configure API Token From f487e59c028e4cd5f2d5f8d2561c0ccf1b1f4736 Mon Sep 17 00:00:00 2001 From: Edgar Cerecerez Date: Fri, 8 Aug 2025 00:11:45 -0600 Subject: [PATCH 13/25] added a new page (#491) * Updating bitbucket integration docs to account for on-prem Removed references to Bitbucket Cloud and left the more ambiguous Bitbucket to account for both on prem and cloud. * Update bitbucket-cloud.md * Delete future-development.md * added mcp doc * bug fixes --- .../mcp-server-integrations.md | 52 +++++++++++++++++++ docs/finishing-touches/_category_.yaml | 4 ++ docs/finishing-touches/docstrings.md | 2 +- docs/finishing-touches/index.md | 15 ++++++ .../finishing-touches/unit-test-generation.md | 2 +- docs/guides/initial-configuration.md | 2 +- docs/guides/issue-creation.md | 2 +- docs/reference/configuration.md | 2 +- sidebars.ts | 11 +++- 9 files changed, 85 insertions(+), 7 deletions(-) create mode 100644 docs/context-enrichment/mcp-server-integrations.md create mode 100644 docs/finishing-touches/index.md diff --git a/docs/context-enrichment/mcp-server-integrations.md b/docs/context-enrichment/mcp-server-integrations.md new file mode 100644 index 00000000..04818323 --- /dev/null +++ b/docs/context-enrichment/mcp-server-integrations.md @@ -0,0 +1,52 @@ +--- +title: MCP integrations +description: MCP integrations allow CodeRabbit to access your documentation, project management tools, knowledge bases, Figma designs, and more. + +--- +:::caution +Pro feature — Early Access only +::: + +You can enable CodeRabbit to connect to external tools and data sources through the Model Context Protocol (MCP) integration. This allows CodeRabbit to serve as the client, and grants it with richer contextual understanding for: + +- Code reviews +- The validation step for code suggestions +- Chat in the PR + +Use the MCP integration as a way to access your documentation, project management tools, knowledge bases, Figma designs, and more. + +## Considerations + +A few things to keep in mind: + +- CodeRabbit acts as the MCP client, not the server. It ingests data. +- The constraint is understanding what MCP data can be helpful for code reviews. See above for how CodeRabbit uses MCP data. +- This approach unlocks integrations in a way that wasn’t possible before. You don’t have to wait for CodeRabbit to have a formal integration, if it has an MCP server, we can connect to it. + +## Setup + +### Configuration steps + +1. Navigate to Integrations Page within your CodeRabbit app settings and select the new MCP Server tab +2. To add a new MCP server, click "Add MCP Integration" and provide your server connection details along with the name +3. Complete the authentication process for your MCP server +4. Enable or disable individual MCP tools for each server + +## How it works + +### During code reviews + +CodeRabbit automatically calls relevant MCP tools during analysis to: + +* Gather additional review context. +* Validate and enhance suggested review comments. + +Enhanced review comments will include enriched insights while maintaining your existing workflow. Tools used during analysis are listed under "Additional context used." + +### In chat interactions + +MCP integration enhances chat by: + +* Retrieving contextual information based on discussion topics +* Accessing external documentation and knowledge bases + diff --git a/docs/finishing-touches/_category_.yaml b/docs/finishing-touches/_category_.yaml index 81a96253..1bd50e46 100644 --- a/docs/finishing-touches/_category_.yaml +++ b/docs/finishing-touches/_category_.yaml @@ -2,3 +2,7 @@ label: Finishing Touches position: 8 collapsible: true collapsed: true +link: + type: generated-index + title: Finishing Touches + slug: /finishing-touches diff --git a/docs/finishing-touches/docstrings.md b/docs/finishing-touches/docstrings.md index c504fa8a..dd4f6467 100644 --- a/docs/finishing-touches/docstrings.md +++ b/docs/finishing-touches/docstrings.md @@ -11,7 +11,7 @@ import ProPlanNotice from '@site/src/components/ProPlanNotice.mdx'; # Docstrings -Docstrings generation is part of the [finishing touches](/future-development#finishing-touches). +Docstrings generation is part of the [Finishing Touches](/finishing-touches). ## Usage diff --git a/docs/finishing-touches/index.md b/docs/finishing-touches/index.md new file mode 100644 index 00000000..0dda55c8 --- /dev/null +++ b/docs/finishing-touches/index.md @@ -0,0 +1,15 @@ +--- +id: finishing-touches +title: Finishing Touches +description: Enhance your pull requests with automated docstrings and unit test generation. +slug: /finishing-touches +--- + +Finishing Touches features help you polish pull requests after review: + +- [Docstrings](/finishing-touches/docstrings) +- [Unit Test Generation](/finishing-touches/unit-test-generation) + +Use these tools to improve documentation and test coverage before merging. + + diff --git a/docs/finishing-touches/unit-test-generation.md b/docs/finishing-touches/unit-test-generation.md index 71fe5431..d2e7ac11 100644 --- a/docs/finishing-touches/unit-test-generation.md +++ b/docs/finishing-touches/unit-test-generation.md @@ -15,7 +15,7 @@ This feature is in beta. # Unit Test Generation -Unit Test Generation is part of the [finishing touches](/future-development#finishing-touches). +Unit Test Generation is part of the [Finishing Touches](/finishing-touches). ## Usage diff --git a/docs/guides/initial-configuration.md b/docs/guides/initial-configuration.md index 5cea2afd..26fc3a2b 100644 --- a/docs/guides/initial-configuration.md +++ b/docs/guides/initial-configuration.md @@ -70,7 +70,7 @@ By default, CodeRabbit writes thorough code reviews with several sub-sections. I - [Sequence diagrams](/reference/configuration#sequence-diagrams): includes a visual diagram of object interactions. - [Assess linked issues](/reference/configuration#assess-linked-issues): assesses how well the pull request addresses any linked issues. - [Related issues](/reference/configuration#related-issues): lists issues found in your issue tracker that might be related to this pull request. -- [Related pull requests](/reference/configuration#realted-prs): lists pull requests that might be related to this pull request. +- [Related pull requests](/reference/configuration#related-prs): lists pull requests that might be related to this pull request. - [Suggested labels](/reference/configuration#suggested-labels): Suggests labels for this pull request. - [Suggested reviewers](/reference/configuration#suggested-reviewers): automatically suggest reviewers for PR - [Poem](/reference/configuration#poem): generates a short poem about this pull request. diff --git a/docs/guides/issue-creation.md b/docs/guides/issue-creation.md index f6228b57..61928e7a 100644 --- a/docs/guides/issue-creation.md +++ b/docs/guides/issue-creation.md @@ -37,7 +37,7 @@ To create Jira issues, ensure you have [configured the Jira integration](../inte ### Linear -Make sure you have [set up the Linear integration](../integrations/issue-integrations.md#linear) to create Linear issues. +Make sure you have [set up the Linear integration](../integrations/issue-integrations.md#Linear) to create Linear issues. ## Tips for Issue Creation diff --git a/docs/reference/configuration.md b/docs/reference/configuration.md index d95fbaa0..14b7e32e 100644 --- a/docs/reference/configuration.md +++ b/docs/reference/configuration.md @@ -1980,7 +1980,7 @@ Specify the scope of learnings to use for the knowledge base. 'local' uses the r You can define a list of paths that guide CodeRabbit to your organization's code guidelines. If you do, then CodeRabbit applies these guidelines to its code reviews. For more -information, see [Code Guidelines](/integrations/knowledge-base#code_guidelines). +information, see [Code Guidelines](/integrations/knowledge-base#code-guidelines). #### Enable code guidelines diff --git a/sidebars.ts b/sidebars.ts index 487a363b..b8459b09 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -127,7 +127,7 @@ const sidebars: SidebarsConfig = { { type: "category", collapsed: true, - label: "Review local changes", + label: "IDE extensions", items: [ "guides/about-vscode", "guides/install-vscode", @@ -137,6 +137,14 @@ const sidebars: SidebarsConfig = { "guides/uninstall-vscode", ], }, + { + type: "category", + collapsed: true, + label: "Context enrichment", + items: [ + "context-enrichment/mcp-server-integrations", + ], + }, { type: "category", collapsed: true, @@ -226,7 +234,6 @@ const sidebars: SidebarsConfig = { "overview/why-coderabbit", "faq", "early-access", - "future-development", "changelog", ], }, From e43429434f6bd2da912a41b5fb9a78299cc23b96 Mon Sep 17 00:00:00 2001 From: Edgar Cerecerez Date: Fri, 8 Aug 2025 00:35:37 -0600 Subject: [PATCH 14/25] fixing lint errors (#492) * Updating bitbucket integration docs to account for on-prem Removed references to Bitbucket Cloud and left the more ambiguous Bitbucket to account for both on prem and cloud. * Update bitbucket-cloud.md * Delete future-development.md * added mcp doc * bug fixes * fixed lint errors. * lint issues continued. --- .../mcp-server-integrations.md | 29 +++++++++---------- docs/finishing-touches/index.md | 2 -- docs/platforms/bitbucket-cloud.md | 2 +- sidebars.ts | 4 +-- 4 files changed, 16 insertions(+), 21 deletions(-) diff --git a/docs/context-enrichment/mcp-server-integrations.md b/docs/context-enrichment/mcp-server-integrations.md index 04818323..3d9334ad 100644 --- a/docs/context-enrichment/mcp-server-integrations.md +++ b/docs/context-enrichment/mcp-server-integrations.md @@ -1,35 +1,35 @@ --- title: MCP integrations description: MCP integrations allow CodeRabbit to access your documentation, project management tools, knowledge bases, Figma designs, and more. - --- + :::caution Pro feature — Early Access only ::: You can enable CodeRabbit to connect to external tools and data sources through the Model Context Protocol (MCP) integration. This allows CodeRabbit to serve as the client, and grants it with richer contextual understanding for: -- Code reviews -- The validation step for code suggestions +- Code reviews +- The validation step for code suggestions - Chat in the PR -Use the MCP integration as a way to access your documentation, project management tools, knowledge bases, Figma designs, and more. +Use the MCP integration as a way to access your documentation, project management tools, knowledge bases, Figma designs, and more. ## Considerations A few things to keep in mind: -- CodeRabbit acts as the MCP client, not the server. It ingests data. -- The constraint is understanding what MCP data can be helpful for code reviews. See above for how CodeRabbit uses MCP data. -- This approach unlocks integrations in a way that wasn’t possible before. You don’t have to wait for CodeRabbit to have a formal integration, if it has an MCP server, we can connect to it. +- CodeRabbit acts as the MCP client, not the server. It ingests data. +- The constraint is understanding what MCP data can be helpful for code reviews. See above for how CodeRabbit uses MCP data. +- This approach unlocks integrations in a way that wasn't possible before. You don't have to wait for CodeRabbit to have a formal integration, if it has an MCP server, we can connect to it. ## Setup ### Configuration steps -1. Navigate to Integrations Page within your CodeRabbit app settings and select the new MCP Server tab -2. To add a new MCP server, click "Add MCP Integration" and provide your server connection details along with the name -3. Complete the authentication process for your MCP server +1. Navigate to Integrations Page within your CodeRabbit app settings and select the new MCP Server tab +2. To add a new MCP server, click "Add MCP Integration" and provide your server connection details along with the name +3. Complete the authentication process for your MCP server 4. Enable or disable individual MCP tools for each server ## How it works @@ -38,8 +38,8 @@ A few things to keep in mind: CodeRabbit automatically calls relevant MCP tools during analysis to: -* Gather additional review context. -* Validate and enhance suggested review comments. +- Gather additional review context. +- Validate and enhance suggested review comments. Enhanced review comments will include enriched insights while maintaining your existing workflow. Tools used during analysis are listed under "Additional context used." @@ -47,6 +47,5 @@ Enhanced review comments will include enriched insights while maintaining your e MCP integration enhances chat by: -* Retrieving contextual information based on discussion topics -* Accessing external documentation and knowledge bases - +- Retrieving contextual information based on discussion topics +- Accessing external documentation and knowledge bases diff --git a/docs/finishing-touches/index.md b/docs/finishing-touches/index.md index 0dda55c8..824fc5e8 100644 --- a/docs/finishing-touches/index.md +++ b/docs/finishing-touches/index.md @@ -11,5 +11,3 @@ Finishing Touches features help you polish pull requests after review: - [Unit Test Generation](/finishing-touches/unit-test-generation) Use these tools to improve documentation and test coverage before merging. - - diff --git a/docs/platforms/bitbucket-cloud.md b/docs/platforms/bitbucket-cloud.md index a708441b..5813e5eb 100644 --- a/docs/platforms/bitbucket-cloud.md +++ b/docs/platforms/bitbucket-cloud.md @@ -11,7 +11,7 @@ CodeRabbit integrates with Bitbucket to enhance code review and collaboration by - Displaying review comments and suggestions directly on merge requests. - Enabling seamless interaction with the CodeRabbit bot for real-time feedback and assistance. -This guide will assist you in effectively integrating CodeRabbit with Bitbucket Cloud. [Click here](https://docs.coderabbit.ai/self-hosted/bitbucket) for instructions integrating Bitbucket Data Center with CodeRabit self-hosted edition. +This guide will assist you in effectively integrating CodeRabbit with Bitbucket Cloud. [Click here](https://docs.coderabbit.ai/self-hosted/bitbucket) for instructions integrating Bitbucket Data Center with CodeRabit self-hosted edition. ## Configure API Token diff --git a/sidebars.ts b/sidebars.ts index b8459b09..31081f0c 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -141,9 +141,7 @@ const sidebars: SidebarsConfig = { type: "category", collapsed: true, label: "Context enrichment", - items: [ - "context-enrichment/mcp-server-integrations", - ], + items: ["context-enrichment/mcp-server-integrations"], }, { type: "category", From c3e91e5fea54d639e2d8653fe818a25dc4bc2a7f Mon Sep 17 00:00:00 2001 From: Harjot Gill Date: Sun, 10 Aug 2025 17:02:57 -0700 Subject: [PATCH 15/25] update rate limits faq --- docs/faq.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index f248b517..630c3570 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -205,13 +205,13 @@ In-trial and open-source plans have lower rate limits than the paid plan. In all The following limits are enforced _per developer_: -| Feature | Free Plan | Trial Plan | OSS Plan | Pro/Lite Plan | -| -------------------------------- | ------------------------------------------ | --------------------------------- | ----------------------------- | ----------------------------- | -| Files per hour | 200/hour | 200/hour | 200/hour | 400/hour | -| Files per PR | 100 | 100 | 100 | 200 | -| Reviews per hour | 3 back-to-back, then 2/hour (Summary only) | 4 back-to-back, then 3/hour | 3 back-to-back, then 2/hour | 5 back-to-back, then 4/hour | -| Reviews per hour (IDE Extension) | 1/hour | 5/hour (Pro trial), 1/hour(Other) | 1/hour | 5/hour (Pro), 1/hour(Lite) | -| Chat | N/A | 25 back-to-back, then 50/hour | 10 back-to-back, then 25/hour | 25 back-to-back, then 50/hour | +| Feature | Free Plan | Trial Plan | OSS Plan | Pro/Lite Plan | +| -------------------------------- | ------------------------------------------ | ----------------------------- | ----------------------------- | ------------------------------------------------------------------------ | +| Files per hour | 200/hour | 200/hour | 200/hour | 400/hour | +| Files per PR | 100 | 100 | 100 | 200 | +| Reviews per hour (Git platforms) | 3 back-to-back, then 2/hour (Summary only) | 4 back-to-back, then 3/hour | 3 back-to-back, then 2/hour | 5 back-to-back, then 4/hour | +| Reviews per hour (IDE Extension) | 2 back-to-back, then 1/hour | 4 back-to-back, then 3/hour | 2 back-to-back, then 1/hour | Pro: 4 back-to-back, then 5/hour.
Lite: 2 back-to-back, then 1/hour. | +| Chat | N/A | 25 back-to-back, then 50/hour | 10 back-to-back, then 25/hour | 25 back-to-back, then 50/hour | ## Integration Guide {#integration-guide} From 65ca0c207e72422ae4ba7371993f62c377b19938 Mon Sep 17 00:00:00 2001 From: Harjot Gill Date: Tue, 12 Aug 2025 22:28:03 -0700 Subject: [PATCH 16/25] update limits --- docs/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq.md b/docs/faq.md index 630c3570..ed5599a8 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -210,7 +210,7 @@ The following limits are enforced _per developer_: | Files per hour | 200/hour | 200/hour | 200/hour | 400/hour | | Files per PR | 100 | 100 | 100 | 200 | | Reviews per hour (Git platforms) | 3 back-to-back, then 2/hour (Summary only) | 4 back-to-back, then 3/hour | 3 back-to-back, then 2/hour | 5 back-to-back, then 4/hour | -| Reviews per hour (IDE Extension) | 2 back-to-back, then 1/hour | 4 back-to-back, then 3/hour | 2 back-to-back, then 1/hour | Pro: 4 back-to-back, then 5/hour.
Lite: 2 back-to-back, then 1/hour. | +| Reviews per hour (IDE Extension) | 1 back-to-back, then 1/hour | 4 back-to-back, then 3/hour | 1 back-to-back, then 1/hour | Pro: 4 back-to-back, then 5/hour.
Lite: 1 back-to-back, then 1/hour. | | Chat | N/A | 25 back-to-back, then 50/hour | 10 back-to-back, then 25/hour | 25 back-to-back, then 50/hour | ## Integration Guide {#integration-guide} From bf13a491a1975d3db8c2763e0937771c099099e9 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 14 Aug 2025 00:27:05 +0000 Subject: [PATCH 17/25] Update schema.v2.json --- static/schema/schema.v2.json | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index b31867ae..a5e67645 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -1063,6 +1063,19 @@ "additionalProperties": false, "default": {}, "description": "checkmake is a linter for Makefiles." + }, + "osvScanner": { + "type": "object", + "properties": { + "enabled": { + "type": "boolean", + "default": true, + "description": "Enable OSV Scanner | OSV Scanner is a tool for vulnerability package scanning | v2.1.0" + } + }, + "additionalProperties": false, + "default": {}, + "description": "OSV Scanner is a tool for vulnerability package scanning." } }, "additionalProperties": false, From fea476867aa1824cdb55dda3a9081342f7ba863b Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 14 Aug 2025 06:46:34 +0000 Subject: [PATCH 18/25] Update schema.v2.json --- static/schema/schema.v2.json | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index a5e67645..b31867ae 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -1063,19 +1063,6 @@ "additionalProperties": false, "default": {}, "description": "checkmake is a linter for Makefiles." - }, - "osvScanner": { - "type": "object", - "properties": { - "enabled": { - "type": "boolean", - "default": true, - "description": "Enable OSV Scanner | OSV Scanner is a tool for vulnerability package scanning | v2.1.0" - } - }, - "additionalProperties": false, - "default": {}, - "description": "OSV Scanner is a tool for vulnerability package scanning." } }, "additionalProperties": false, From cc01026208cf21428a6ba53a95769a1365fd1988 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 14 Aug 2025 06:47:15 +0000 Subject: [PATCH 19/25] Update schema.v2.json --- static/schema/schema.v2.json | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index b31867ae..2ea3b0b0 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -1063,6 +1063,19 @@ "additionalProperties": false, "default": {}, "description": "checkmake is a linter for Makefiles." + }, + "osvScanner": { + "type": "object", + "properties": { + "enabled": { + "type": "boolean", + "default": true, + "description": "Enable OSV Scanner | OSV Scanner is a tool for vulnerability package scanning | v2.1.0" + } + }, + "additionalProperties": false, + "default": {}, + "description": "OSV Scanner is a tool for vulnerability package scanning." } }, "additionalProperties": false, @@ -1240,6 +1253,27 @@ }, "additionalProperties": false, "default": {} + }, + "mcp": { + "type": "object", + "properties": { + "usage": { + "type": "string", + "enum": ["auto", "enabled", "disabled"], + "default": "auto", + "description": "MCP | Enable the MCP knowledge base integration. 'auto' disables the integration for public repositories." + }, + "disabled_servers": { + "type": "array", + "items": { + "type": "string" + }, + "default": [], + "description": "MCP Disabled Servers | Specify MCP server labels to disable (case-insensitive). These servers will be excluded from reviews and knowledge base queries." + } + }, + "additionalProperties": false, + "default": {} } }, "additionalProperties": false, From b52160f2587bc06df699f3e02fc3f2ff9f86217e Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 14 Aug 2025 06:59:45 +0000 Subject: [PATCH 20/25] Update schema.v2.json --- static/schema/schema.v2.json | 34 ---------------------------------- 1 file changed, 34 deletions(-) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index 2ea3b0b0..b31867ae 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -1063,19 +1063,6 @@ "additionalProperties": false, "default": {}, "description": "checkmake is a linter for Makefiles." - }, - "osvScanner": { - "type": "object", - "properties": { - "enabled": { - "type": "boolean", - "default": true, - "description": "Enable OSV Scanner | OSV Scanner is a tool for vulnerability package scanning | v2.1.0" - } - }, - "additionalProperties": false, - "default": {}, - "description": "OSV Scanner is a tool for vulnerability package scanning." } }, "additionalProperties": false, @@ -1253,27 +1240,6 @@ }, "additionalProperties": false, "default": {} - }, - "mcp": { - "type": "object", - "properties": { - "usage": { - "type": "string", - "enum": ["auto", "enabled", "disabled"], - "default": "auto", - "description": "MCP | Enable the MCP knowledge base integration. 'auto' disables the integration for public repositories." - }, - "disabled_servers": { - "type": "array", - "items": { - "type": "string" - }, - "default": [], - "description": "MCP Disabled Servers | Specify MCP server labels to disable (case-insensitive). These servers will be excluded from reviews and knowledge base queries." - } - }, - "additionalProperties": false, - "default": {} } }, "additionalProperties": false, From 2da1e6657f3800eb8d76e2af6aa14bd2dade180f Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 14 Aug 2025 07:00:35 +0000 Subject: [PATCH 21/25] Update schema.v2.json --- static/schema/schema.v2.json | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index b31867ae..2ea3b0b0 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -1063,6 +1063,19 @@ "additionalProperties": false, "default": {}, "description": "checkmake is a linter for Makefiles." + }, + "osvScanner": { + "type": "object", + "properties": { + "enabled": { + "type": "boolean", + "default": true, + "description": "Enable OSV Scanner | OSV Scanner is a tool for vulnerability package scanning | v2.1.0" + } + }, + "additionalProperties": false, + "default": {}, + "description": "OSV Scanner is a tool for vulnerability package scanning." } }, "additionalProperties": false, @@ -1240,6 +1253,27 @@ }, "additionalProperties": false, "default": {} + }, + "mcp": { + "type": "object", + "properties": { + "usage": { + "type": "string", + "enum": ["auto", "enabled", "disabled"], + "default": "auto", + "description": "MCP | Enable the MCP knowledge base integration. 'auto' disables the integration for public repositories." + }, + "disabled_servers": { + "type": "array", + "items": { + "type": "string" + }, + "default": [], + "description": "MCP Disabled Servers | Specify MCP server labels to disable (case-insensitive). These servers will be excluded from reviews and knowledge base queries." + } + }, + "additionalProperties": false, + "default": {} } }, "additionalProperties": false, From 118d692dc3e81efa564d7d7bd02a1b9d4c24972d Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 14 Aug 2025 22:47:03 +0000 Subject: [PATCH 22/25] Update schema.v2.json --- static/schema/schema.v2.json | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index 2ea3b0b0..56e4b78d 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -1090,6 +1090,11 @@ "chat": { "type": "object", "properties": { + "art": { + "type": "boolean", + "default": true, + "description": "Generate art in response to chat messages. CodeRabbit expresses emotions as either ASCII or Emoji art." + }, "auto_reply": { "type": "boolean", "default": true, From 4bda6c51aac35507eb892addf2b9476f05285428 Mon Sep 17 00:00:00 2001 From: Edgar Cerecerez Date: Thu, 14 Aug 2025 21:16:44 -0600 Subject: [PATCH 23/25] Update README.md --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 8167aa97..9b43590c 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,13 @@ CodeRabbit Logo

+====================== +# CodeRabbit docs have moved over to Mintlify as a private repo. These docs are no longer mantained. + + + +======================= # CodeRabbit Documentation Welcome to the official docs for [**CodeRabbit**](https://coderabbit.ai), the code review dev tool that helps you ship quality code faster. From 2038915d4672fc56db150b27350a21b3a953fa8d Mon Sep 17 00:00:00 2001 From: Edgar Cerecerez Date: Thu, 14 Aug 2025 21:17:17 -0600 Subject: [PATCH 24/25] Update README.md --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9b43590c..ba4cd53a 100644 --- a/README.md +++ b/README.md @@ -3,13 +3,14 @@ CodeRabbit Logo

-====================== -# CodeRabbit docs have moved over to Mintlify as a private repo. These docs are no longer mantained. +--- +# CodeRabbit docs have moved over to Mintlify as a private repo. These docs are no longer mantained. + +--- -======================= # CodeRabbit Documentation Welcome to the official docs for [**CodeRabbit**](https://coderabbit.ai), the code review dev tool that helps you ship quality code faster. From 999426584c2cfa6a1b2697f116ba45c574921e65 Mon Sep 17 00:00:00 2001 From: Edgar Cerecerez Date: Thu, 14 Aug 2025 21:18:12 -0600 Subject: [PATCH 25/25] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ba4cd53a..a88a85a7 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ --- -# CodeRabbit docs have moved over to Mintlify as a private repo. These docs are no longer mantained. +# CodeRabbit docs have moved over to Mintlify as a private repo. These docs are no longer maintained. ---