From 34c941262da8d66bf2d8273b2d3824c8cb7642eb Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 12 Jun 2025 05:59:36 +0000 Subject: [PATCH 01/10] 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 e3dd3eee..3fd34c48 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -925,19 +925,6 @@ "additionalProperties": false, "description": "HTMLHint is a static code analysis tool for HTML files.", "default": {} - }, - "checkmake": { - "type": "object", - "properties": { - "enabled": { - "type": "boolean", - "default": true, - "description": "Enable checkmake | checkmake is a linter for Makefiles. | v0.2.2" - } - }, - "additionalProperties": false, - "default": {}, - "description": "checkmake is a linter for Makefiles." } }, "additionalProperties": false, From fd91024fe49ea92b6793991ecd4b4d0f8174fba2 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 12 Jun 2025 08:25:31 +0000 Subject: [PATCH 02/10] 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 3fd34c48..e3dd3eee 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -925,6 +925,19 @@ "additionalProperties": false, "description": "HTMLHint is a static code analysis tool for HTML files.", "default": {} + }, + "checkmake": { + "type": "object", + "properties": { + "enabled": { + "type": "boolean", + "default": true, + "description": "Enable checkmake | checkmake is a linter for Makefiles. | v0.2.2" + } + }, + "additionalProperties": false, + "default": {}, + "description": "checkmake is a linter for Makefiles." } }, "additionalProperties": false, From 652c7fb0a7ee66c43433c4f937d76609d8f2d7be Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 12 Jun 2025 11:56:51 +0000 Subject: [PATCH 03/10] Update schema.v2.json --- static/schema/schema.v2.json | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index e3dd3eee..91a2d344 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -95,7 +95,17 @@ "de-LU", "fr-FR", "bg-BG", - "bg" + "bg", + "he-IL", + "he", + "hi-IN", + "hi", + "vi-VN", + "vi", + "th-TH", + "th", + "bn-BD", + "bn" ], "default": "en-US", "description": "Set the language for reviews by using the corresponding ISO language code." @@ -1196,7 +1206,17 @@ "de-LU", "fr-FR", "bg-BG", - "bg" + "bg", + "he-IL", + "he", + "hi-IN", + "hi", + "vi-VN", + "vi", + "th-TH", + "th", + "bn-BD", + "bn" ], "default": "en-US", "description": "Set the language for docstrings by using the corresponding ISO language code." From 2132e489c1ce41f0894fea674f7a5035d741de5d Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 12 Jun 2025 12:08:51 +0000 Subject: [PATCH 04/10] Update schema.v2.json --- static/schema/schema.v2.json | 24 ++---------------------- 1 file changed, 2 insertions(+), 22 deletions(-) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index 91a2d344..e3dd3eee 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -95,17 +95,7 @@ "de-LU", "fr-FR", "bg-BG", - "bg", - "he-IL", - "he", - "hi-IN", - "hi", - "vi-VN", - "vi", - "th-TH", - "th", - "bn-BD", - "bn" + "bg" ], "default": "en-US", "description": "Set the language for reviews by using the corresponding ISO language code." @@ -1206,17 +1196,7 @@ "de-LU", "fr-FR", "bg-BG", - "bg", - "he-IL", - "he", - "hi-IN", - "hi", - "vi-VN", - "vi", - "th-TH", - "th", - "bn-BD", - "bn" + "bg" ], "default": "en-US", "description": "Set the language for docstrings by using the corresponding ISO language code." From 3234e405cc440fec456fabce8aa66098dbd8ee46 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 12 Jun 2025 13:07:55 +0000 Subject: [PATCH 05/10] Update schema.v2.json --- static/schema/schema.v2.json | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index e3dd3eee..91a2d344 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -95,7 +95,17 @@ "de-LU", "fr-FR", "bg-BG", - "bg" + "bg", + "he-IL", + "he", + "hi-IN", + "hi", + "vi-VN", + "vi", + "th-TH", + "th", + "bn-BD", + "bn" ], "default": "en-US", "description": "Set the language for reviews by using the corresponding ISO language code." @@ -1196,7 +1206,17 @@ "de-LU", "fr-FR", "bg-BG", - "bg" + "bg", + "he-IL", + "he", + "hi-IN", + "hi", + "vi-VN", + "vi", + "th-TH", + "th", + "bn-BD", + "bn" ], "default": "en-US", "description": "Set the language for docstrings by using the corresponding ISO language code." From f066cddce1fb99345a9961751131222fb8b7c42e Mon Sep 17 00:00:00 2001 From: Jason McIntosh Date: Thu, 12 Jun 2025 09:28:46 -0400 Subject: [PATCH 06/10] Add documentation for RBAC (#379) * Add a page about RBAC. --- docs/getting-started/adding-organizations.md | 4 + .../subscription-management.md | 4 + docs/guides/roles.md | 138 ++++++++++++++++++ sidebars.ts | 8 +- 4 files changed, 153 insertions(+), 1 deletion(-) create mode 100644 docs/guides/roles.md diff --git a/docs/getting-started/adding-organizations.md b/docs/getting-started/adding-organizations.md index 5f4b635b..66741daa 100644 --- a/docs/getting-started/adding-organizations.md +++ b/docs/getting-started/adding-organizations.md @@ -21,3 +21,7 @@ This will grant CodeRabbit access to the selected organization, allowing it to: - Access user email addresses (read-only) > Note: Organizations control which applications are allowed to access their private data. You may need organization admin approval to complete this process. + +## What's next {#whats-next} + +- [Manage your subscription](/getting-started/subscription-management) diff --git a/docs/getting-started/subscription-management.md b/docs/getting-started/subscription-management.md index 4483ce78..6eabd3ee 100644 --- a/docs/getting-started/subscription-management.md +++ b/docs/getting-started/subscription-management.md @@ -57,3 +57,7 @@ To modify the number of seats in your subscription: ![Changing your plan](../../static/img/getting-started/edit-subscription.png) ![Changing your plan](../../static/img/getting-started/change-seats.png) + +## What's next {#whats-next} + +- [Control administrative access](/guides/roles) diff --git a/docs/guides/roles.md b/docs/guides/roles.md new file mode 100644 index 00000000..c919f57d --- /dev/null +++ b/docs/guides/roles.md @@ -0,0 +1,138 @@ +--- +title: Control administrative access +description: Using the role-based authorization features of CodeRabbit +--- + +You can control which CodeRabbit +administrative features are available to your organization's user accounts by +assigning and updating account roles. + +## Overview of CodeRabbit roles {#overview} + +Every CodeRabbit account has exactly one role for each organization +that account is associated with. +For example, if you belong to two GitHub-based organizations that use +CodeRabbit, then you have one CodeRabbit role set for each of those two +organizations. + +CodeRabbit roles determine your ability to read or change various +billing, account management, and other administrative functions related to +an organization. The roles are as follows: + +- **Admin**: allows full read/write access to all CodeRabbit administrative features. +- **Member**: allows read-only access to a limited set of administrative settings. This role + is appropriate for most developers in an organization. +- **Billing Admin**: allows read/write access to features specific + to a subscription and billing management, and limited access to other administrative features. + +CodeRabbit users with the **Admin** role can modify the roles of other users in the +organization. + +For a complete list of the administrative functions available to each role, see +[Role permissions](#permissions). + +### CodeRabbit roles and Git platform roles {#and-upstream} + +Modifying an account's CodeRabbit role doesn't have any "upstream" +effect on that account's role or permissions in your organization's Git platform. +Similarly, changes to an account's role on your organization's Git platform don't +affect that account's CodeRabbit role. + +For example, if you have CodeRabbit integrated with a GitHub organization, and you change an account's CodeRabbit role from **Member** to **Admin**, then that account's +permission or ownership level with your GitHub organization doesn't change as a result. + +### CodeRabbit roles and developer features {#and-features} + +CodeRabbit roles affect only access to administrative features. Roles have no effect on using CodeRabbit developer features, such as automated code reviews. + +For example, if an organization has a Pro-tier +CodeRabbit account, then any user account with a seat assigned to it can use Pro-tier features with the organization's private repositories, regardless of that account's role. + +For more information on seat and subscription management, see [Manage your subscription](/getting-started/subscription-management). + +## Default roles {#defaults} + +CodeRabbit assigns every user account in your organization a default role, +using the following metrics: + +- If a user has an ownership-level role with the Git platform organization—for example, + **Admin** on GitHub, or **Owner** on Bitbucket—then that user receives the default + CodeRabbit role of **Admin**. +- Otherwise, the user receives the **Member** role by default. + +You can update a user's role from its default setting by following the steps detailed in the next section. This requires that your own account +has an **Admin** role with the organization. + +CodeRabbit applies these defaults only when initially setting up for an +account within an organization. Subsequent "upstream" role changes don't affect +an account's CodeRabbit role. + +## View or set roles {#how-to} + +You can view and set roles from the CodeRabbit dashboard, as detailed in the +following sections. + +### View roles {#view-roles} + +To view a list of your organization's role assignments, follow these steps: + +1. Go to the [CodeRabbit dashboard](https://app.coderabbit.ai/settings/repositories). +1. At the top of the sidebar, select the organization whose user roles you want to view. +1. On the sidebar, click **Subscription**. + +This displays a table of all of the CodeRabbit **Admin** and **Member** accounts associated with the selected +organization. In this table, the **Role** column displays the CodeRabbit role for +each account. + +To view a list of accounts with the **Billing Admin** role, click the **Billing Admins** tab located above the table of user accounts. + +### Set roles {#set-roles} + +:::note +To modify users' CodeRabbit accounts, your own account must have the **Admin** role within your organization. +::: + +To change a user account's CodeRabbit role, follow these steps: + +1. Go to your organization's list of user accounts, as detailed in the previous section. + If you have the **Admin** role within this organization, then the **Role** column in the user accounts table contains selectable menus. +1. Click the menu in the user's **Role** column, and select the appropriate role from + the list. + +The only roles you can assign through this method are **Admin** and **Member**. +You can't grant the **Billing Admin** role to an existing user account. To add an account with the **Billing Admin** role, see the next section. + +### Add billing admin accounts {#billing} + +:::note +Billing Admin users don't require CodeRabbit seat licenses. You can add Billing Admin users regardless of how many seat licenses you have available. +::: + +To add a CodeRabbit user account with the **Billing Admin** role, follow these steps: + +1. Go to your organization's list of user accounts, as detailed in [View roles](#view-roles). +1. Click **Invite Billing Admin**. +1. Enter the name and email address of the billing administrator who you want to invite to the organization. + +This sends an email to the address that you specified. After the recipient completes the process of joining your organization in CodeRabbit, then their record appears in the user accounts list, under the **Billing Admins** tab. + +## Role permissions {#permissions} + +The following table lists the CodeRabbit administrative functionality +available to each of the CodeRabbit roles. + +| Resource | Admin | Member | Billing Admin | +| ----------------------- | ---------- | --------- | ------------- | +| Learning Resources | Read/Write | Read-only | No access | +| Metrics/Dashboard | Read/Write | No access | No access | +| Reports | Read/Write | Read-only | No access | +| Integrations | Read/Write | Read-only | No access | +| Repository Settings | Read/Write | Read-only | No access | +| Organization Settings | Read/Write | Read-only | No access | +| User Management | Read/Write | Read-only | Read-only | +| Subscription Management | Read/Write | Read-only | Read/Write | +| Billing Management | Read/Write | No access | Read/Write | + +## What's next {#whats-next} + +- [Manage your subscription](/getting-started/subscription-management) diff --git a/sidebars.ts b/sidebars.ts index 3deb1cb8..91cab161 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -68,6 +68,12 @@ const sidebars: SidebarsConfig = { }, ], }, + { + type: "category", + collapsed: true, + label: "Manage your account", + items: ["getting-started/subscription-management", "guides/roles"], + }, { type: "category", collapsed: true, @@ -77,6 +83,7 @@ const sidebars: SidebarsConfig = { "integrations/knowledge-base", "guides/review-instructions", "tools/tools", + "guides/roles", ], }, { @@ -198,7 +205,6 @@ const sidebars: SidebarsConfig = { label: "Resources", items: [ "getting-started/support", - "getting-started/subscription-management", "overview/why-coderabbit", "faq", "early-access", From 43b2d8952cd1810a6b34e64e03ca08e2395a3396 Mon Sep 17 00:00:00 2001 From: Jason McIntosh Date: Thu, 12 Jun 2025 09:46:36 -0400 Subject: [PATCH 07/10] Clarify several best practices. (#389) --- docs/guides/setup-best-practices.md | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/docs/guides/setup-best-practices.md b/docs/guides/setup-best-practices.md index 81143fd8..d45ec801 100644 --- a/docs/guides/setup-best-practices.md +++ b/docs/guides/setup-best-practices.md @@ -64,23 +64,21 @@ works with your individual repositories. CodeRabbit gives you two ways to configure how it works with your team's repositories: -- The [Repositories](https://app.coderabbit.ai/settings/repositories) page of the - Dashboard +- The **Organization Settings** and **Repositories** pages of [the + CodeRabbit web interface](https://app.coderabbit.ai/login) - A [`coderabbit.yaml` file](/getting-started/configure-coderabbit/) in your repository -The graphical UI of the Repositories page lets you set up your per-repository -preferences more rapidly, and can help you get familiar with CodeRabbit configuration options. +The web interface lets you set up your organization's code review +preferences rapidly, and can help you get familiar with CodeRabbit configuration options. -Once you are ready to fine-tune the ways that CodeRabbit works with your repositories, -we recommend adding a `coderabbit.yaml` file to each one. This file has several -advantages over using only the Dashboard: +We recommend adding a `coderabbit.yaml` file to repositories, as well. Using this file has several advantages over using only the web interface: -- It applies version control to your repository's CodeRabbit settings. +- It applies version control to your repository's CodeRabbit settings, letting you track changes, view configuration history, and revert to previous configurations as needed. - During code reviews, CodeRabbit loads the file along with rest of your repository. This means that you can include setting changes as part of a pull request, and CodeRabbit both analyzes and applies these settings during its review. - The file makes the repository's CodeRabbit settings transparent to all of the repository's contributors. Repository-level settings defined by a `coderabbit.yaml` take precedence over the -settings defined for that repository in the Dashboard. +settings defined for that repository or for your organization using the CodeRabbit web interface. For more information, see [Add a configuration file](/getting-started/configure-coderabbit/). @@ -89,14 +87,14 @@ For more information, see [Add a configuration file](/getting-started/configure- If your repository contains a lot of data or other content that CodeRabbit doesn't need for code review context, then you can include _path filters_ in your repository configuration. For example, a filter of `!dist/**` tells CodeRabbit -to disregard everything in your reposistory's top-level `dist` directory when +to disregard everything in your repository's top-level `dist` directory when preparing a code review. Reducing the number of contextual files that CodeRabbit needs to read and analyze when preparing a code review can help make its code reviews faster. You can define path filters using the CodeRabbit -web interface, or with [a configuration file](/getting-started/configure-coderabbit/). +web interface, or with [a `coderabbit.yaml` file](/getting-started/configure-coderabbit/). ### Trust the defaults {#defaults} @@ -108,7 +106,7 @@ CodeRabbit gives you control over a number of its core code-review features, let tools](/tools) that are available to it during code reviews. This helps CodeRabbit keep its reviews broad and flexible. - **Knowledge base**: CodeRabbit [knowledge base](/integrations/knowledge-base/) features, including learnings and issue tracking, can require data retention. If your organization needs to meet stricter data-retention policies, then you can opt out of using these features. -You can configure your use of the above features using the CodeRabbit web interface, or [a configuration file](/getting-started/configure-coderabbit/). +You can configure your use of the above features using the CodeRabbit web interface, or [a `coderabbit.yaml` file](/getting-started/configure-coderabbit/). ### Write specific CI/CD error messages {#pipeline} From 3ab5c506d77f4f4d0f6a90676ab37aea8777c6c9 Mon Sep 17 00:00:00 2001 From: Howon Lee Date: Thu, 12 Jun 2025 17:31:28 -0700 Subject: [PATCH 08/10] Unit test gen docs (#398) * thinky * thinky * lets not lmao * thingy * reference * let them ask the question * thinky * looks weird otherwise --------- Co-authored-by: Howon Lee --- docs/changelog.md | 14 +++++ docs/finishing-touches/docstrings.md | 2 +- .../finishing-touches/unit-test-generation.md | 57 +++++++++++++++++++ docs/reference/review-commands.md | 9 +-- sidebars.ts | 1 + 5 files changed, 78 insertions(+), 5 deletions(-) create mode 100644 docs/finishing-touches/unit-test-generation.md diff --git a/docs/changelog.md b/docs/changelog.md index 9d40ab2b..240fbdfa 100644 --- a/docs/changelog.md +++ b/docs/changelog.md @@ -15,6 +15,20 @@ We're excited to announce that two new static analysis tools are now supported o - [Checkmake](https://github.com/mrtazz/checkmake) is a linter for Makefiles that helps ensure your build scripts follow best practices and maintain consistency. +## June 10, 2025 + +### Unit Test Generation, Early Access + +We're excited to announce that our new unit test generation feature is now available in early access! CodeRabbit can now automatically generate unit tests for your code changes. + +Key capabilities: + +- **Intelligent Test Generation**: Automatically creates unit tests that cover edge cases, error scenarios, and core functionality +- **Context-Aware**: Generates tests that understand your existing codebase patterns and testing conventions +- **One-Click Integration**: Simply comment `@coderabbitai auto-generate unit tests` on any pull request or specific file, or click on the checkbox available in the walkthrough comment for Early Access customers. + +You can customize the generated tests to fit your specific requirements. + ## June 5, 2025 ### Enhanced Static Analysis: Dotenv Linter and Pylint Support diff --git a/docs/finishing-touches/docstrings.md b/docs/finishing-touches/docstrings.md index 235e7398..c504fa8a 100644 --- a/docs/finishing-touches/docstrings.md +++ b/docs/finishing-touches/docstrings.md @@ -15,7 +15,7 @@ Docstrings generation is part of the [finishing touches](/future-development#fin ## Usage -Once you are done with your pull request and its reviews, you may want to perform finishing touches to your code, such as adding in-code documentation. You can request CodeRabbit to generate docstrings by typing `@coderabbitai generate docstrings` in a comment under that pull request. +Once you are done with your pull request and its reviews, you may want to perform finishing touches to your code, such as adding in-code documentation. You can request CodeRabbit to generate docstrings by typing `@coderabbitai generate docstrings` in a comment under that pull request or by clicking the **Generate Docstrings** checkbox under **Finishing Touches** in the CodeRabbit Walkthrough. Once sent, CodeRabbit will perform the following actions: diff --git a/docs/finishing-touches/unit-test-generation.md b/docs/finishing-touches/unit-test-generation.md new file mode 100644 index 00000000..57c5e211 --- /dev/null +++ b/docs/finishing-touches/unit-test-generation.md @@ -0,0 +1,57 @@ +--- +title: Generate unit tests +description: Automated Unit Test Generation with CodeRabbit +--- + +```mdx-code-block +import ProPlanNotice from '@site/src/components/ProPlanNotice.mdx'; + + +``` + +:::warning +This feature is [experimental](/early-access#experiments). +::: + +# Unit Test Generation + +Unit Test Generation is part of the [finishing touches](/future-development#finishing-touches). + +Unit Test Generation is an Early Access Experimental feature. + +## Usage + +Once you are done with your pull request and its reviews, you may want to perform finishing touches to your code, such as adding unit tests. You can request CodeRabbit to generate unit tests by typing `@coderabbitai auto-generate unit tests` in a comment under that pull request or by clicking a checkbox under **Generate Unit Tests** in the CodeRabbit Walkthrough. + +Once sent, CodeRabbit will perform the following actions: + +- The CodeRabbit agent will examine your code for places where it needs tests +- Unit tests will be generated for the PR, in a separate PR, in the same PR in a new commit, or in a comment to copy-paste, depending on your choice +- If (and only if) you choose to generate the unit tests in a separate PR, CodeRabbit will examine your GitHub checks (build steps and tests and such) and adjust the PR to deal with build failures, test failures and similar. + +## Path Instructions + +You can customize the generated unit tests by providing instructions based on file paths in your `.coderabbit.yaml`. The `path` is a [minimatch](https://github.com/isaacs/minimatch) pattern. + +```yaml +code_generation: + unit_tests: + path_instructions: + - path: "**/*.ts" + instructions: | + Use vitest for testing framework. + Generate comprehensive test cases including edge cases and error conditions. + Do not omit the imports; the test file must be valid. +``` + +## Supported software forges + +These software forges are supported: + +- GitHub + +## Supported CI/CD systems + +These CI/CD systems are supported for post-generation adjustments: + +- GitHub actions diff --git a/docs/reference/review-commands.md b/docs/reference/review-commands.md index 011bf9d5..cb50b59c 100644 --- a/docs/reference/review-commands.md +++ b/docs/reference/review-commands.md @@ -29,10 +29,11 @@ CodeRabbit through chat, see [Interact with CodeRabbit reviews](/guides/code-rev ## Documentation commands -| Command | Description | Use Case | -| ----------------------------------- | -------------------------------------------- | --------------------------------------------------- | -| `@coderabbitai generate docstrings` | Generates docstrings for functions in the PR | When you need automatic documentation for your code | -| `@coderabbitai configuration` | Shows current CodeRabbit settings | When you need to check or export your configuration | +| Command | Description | Use Case | +| ---------------------------------------- | -------------------------------------------- | --------------------------------------------------- | +| `@coderabbitai generate docstrings` | Generates docstrings for functions in the PR | When you need automatic documentation for your code | +| `@coderabbitai auto-generate unit tests` | Generates unit tests for the PR | When you need automatic unit testing for your code | +| `@coderabbitai configuration` | Shows current CodeRabbit settings | When you need to check or export your configuration | ## Agentic chat commands diff --git a/sidebars.ts b/sidebars.ts index 91cab161..3d56f2b7 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -103,6 +103,7 @@ const sidebars: SidebarsConfig = { items: [ "integrations/code-graph-analysis", "finishing-touches/docstrings", + "finishing-touches/unit-test-generation", ], }, ], From 9e460475a6afd14b2e341d5a7657cd745455fca1 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 13 Jun 2025 03:28:43 +0000 Subject: [PATCH 09/10] Update schema.v2.json --- static/schema/schema.v2.json | 24 ++---------------------- 1 file changed, 2 insertions(+), 22 deletions(-) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index 91a2d344..e3dd3eee 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -95,17 +95,7 @@ "de-LU", "fr-FR", "bg-BG", - "bg", - "he-IL", - "he", - "hi-IN", - "hi", - "vi-VN", - "vi", - "th-TH", - "th", - "bn-BD", - "bn" + "bg" ], "default": "en-US", "description": "Set the language for reviews by using the corresponding ISO language code." @@ -1206,17 +1196,7 @@ "de-LU", "fr-FR", "bg-BG", - "bg", - "he-IL", - "he", - "hi-IN", - "hi", - "vi-VN", - "vi", - "th-TH", - "th", - "bn-BD", - "bn" + "bg" ], "default": "en-US", "description": "Set the language for docstrings by using the corresponding ISO language code." From 8d5d1ca74e893f005ce1f3e935b9deabfbc7f251 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 13 Jun 2025 03:56:14 +0000 Subject: [PATCH 10/10] Update schema.v2.json --- static/schema/schema.v2.json | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json index e3dd3eee..91a2d344 100644 --- a/static/schema/schema.v2.json +++ b/static/schema/schema.v2.json @@ -95,7 +95,17 @@ "de-LU", "fr-FR", "bg-BG", - "bg" + "bg", + "he-IL", + "he", + "hi-IN", + "hi", + "vi-VN", + "vi", + "th-TH", + "th", + "bn-BD", + "bn" ], "default": "en-US", "description": "Set the language for reviews by using the corresponding ISO language code." @@ -1196,7 +1206,17 @@ "de-LU", "fr-FR", "bg-BG", - "bg" + "bg", + "he-IL", + "he", + "hi-IN", + "hi", + "vi-VN", + "vi", + "th-TH", + "th", + "bn-BD", + "bn" ], "default": "en-US", "description": "Set the language for docstrings by using the corresponding ISO language code."