From 92039f1c17cf89fd529eaa1ac779f62aca8928eb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Tue, 3 Mar 2026 13:46:50 +0000 Subject: [PATCH 1/4] update date + context to match email --- ...-03-github-integration-settings-changes.md | 25 +++++++++++++------ 1 file changed, 18 insertions(+), 7 deletions(-) diff --git a/docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md b/docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md index c827ce5838..917b84c0fa 100644 --- a/docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md +++ b/docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md @@ -9,27 +9,38 @@ rss_href: /feed_rss_created.xml We are making two changes to the GitHub integration settings over the coming weeks. Both are handled automatically - you don't need to take any action. -- [**AI-enhanced comments (Beta) being deprecated for GitHub**](#ai-enhanced-comments) — AI-enhanced comments are being replaced by the AI Reviewer on March 16, 2026. +- [**AI-enhanced comments (Beta) being deprecated for GitHub**](#ai-enhanced-comments) — AI-enhanced comments are being replaced by the [AI Reviewer](../../codacy-ai/codacy-ai.md#pr-reviewer) on March 17, 2026. - [**Coverage summary moving to Pull request review**](#coverage-summary) — the Coverage summary setting is being removed; coverage data will soon be included in the Pull request review comment. -## AI-enhanced comments (Beta) being deprecated on March 16, 2026 {: id="ai-enhanced-comments"} +## AI-enhanced comments (Beta) being deprecated on March 17, 2026 {: id="ai-enhanced-comments"} -Codacy is deprecating the AI-enhanced comments (Beta) feature in favour of the AI Reviewer, which provides a more accurate, comprehensive, and streamlined experience for identifying and addressing issues. +Codacy is deprecating the AI-enhanced comments (Beta) feature in favour of the [AI Reviewer](../../codacy-ai/codacy-ai.md#ai-reviewer), which provides a more accurate, comprehensive, and context-aware experience for identifying and addressing issues. + +On March 17, 2026, Codacy will migrate all repositories and organizations that have **AI-enhanced comments** enabled to the [AI Reviewer](../../codacy-ai/codacy-ai.md#ai-reviewer) and remove the setting. -On March 16, 2026, Codacy will migrate all repositories and organizations that have **AI-enhanced comments** enabled to the AI Reviewer and remove the setting. !!! note Organizations with contractual restrictions on AI providers or content analysis scope will not be automatically migrated to the AI Reviewer. For these organizations, AI-enhanced comments will simply be disabled. The AI Reviewer can be enabled at any time from your [integration settings](../../repositories-configure/integrations/github-integration.md#ai-reviewer). For more information, contact your account manager or . ### What to expect -- The AI-enhanced comments (Beta) setting will be removed on March 16, 2026. -- If you had AI-enhanced comments enabled at repository or organization level, those will be migrated to the AI Reviewer accordingly. +- On March 17, 2026, the AI-enhanced comments setting will be removed and any repository or organization where it is enabled will be migrated to the AI Reviewer. +- Repositories where AI-enhanced comments are not enabled will not have the AI Reviewer enabled automatically. - The AI Reviewer defaults to **manual** mode, so your team won't receive unexpected reviews. ### What do you need to do? -Nothing. Codacy will handle the migration automatically. If you have any further questions, contact . +Nothing is required. Codacy will handle the migration automatically. + +If you prefer, you can enable the AI Reviewer now in your organization and repository integration settings. If you enable it before March 17, 2026, we recommend manually disabling **AI-enhanced comments** at the same time to avoid duplicate comments on Pull Requests. + +If you have any further questions, contact . + +### Why this change + +- The [AI Reviewer](../../codacy-ai/codacy-ai.md#pr-reviewer) uses broader context from source code and PR metadata (and Jira tickets, if enabled), which improves accuracy and reduces noise. +- You can guide reviews with custom instructions using a `review.md` file in your repository. +- You can trigger reviews on demand from Pull Requests using the **Run review** button. ## Coverage summary moving to Pull request review {: id="coverage-summary"} From f7435bb7d71992b127369c5a3c43aef714b77de0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Fri, 24 Apr 2026 11:35:27 +0100 Subject: [PATCH 2/4] docs: document that open source GitHub repos require Status checks enabled for analysis For open source repositories on GitHub, Codacy no longer runs analysis when the Status checks integration setting is disabled. Added a warning to the GitHub integration page and expanded the troubleshooting FAQ to include this as a reason analysis may not run. Co-Authored-By: Claude Sonnet 4.6 --- .../why-isnt-my-public-repository-being-analyzed.md | 7 ++++++- .../integrations/github-integration.md | 3 +++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/faq/troubleshooting/why-isnt-my-public-repository-being-analyzed.md b/docs/faq/troubleshooting/why-isnt-my-public-repository-being-analyzed.md index 3fb5cf63ca..8f79619acd 100644 --- a/docs/faq/troubleshooting/why-isnt-my-public-repository-being-analyzed.md +++ b/docs/faq/troubleshooting/why-isnt-my-public-repository-being-analyzed.md @@ -1,3 +1,8 @@ # Why isn't my public repository being analyzed? -Codacy only analyzes open source repositories if the admin of the repository is a committer to that repository. +Codacy only analyzes open source repositories on GitHub if both of the following conditions are met: + +- The admin of the repository is a committer to that repository. +- **Status checks** is enabled in the [GitHub integration settings](../../repositories-configure/integrations/github-integration.md#status-checks) for the repository, either directly or via the [organization defaults](../../organizations/integrations/default-git-provider-integration-settings.md). + +If **Status checks** is disabled, Codacy will not run analysis for open source repositories on GitHub. diff --git a/docs/repositories-configure/integrations/github-integration.md b/docs/repositories-configure/integrations/github-integration.md index 9d49e5e1bc..d9b74dba6c 100644 --- a/docs/repositories-configure/integrations/github-integration.md +++ b/docs/repositories-configure/integrations/github-integration.md @@ -26,6 +26,9 @@ Depending on the options that you enable, Codacy will automatically update pull Adds a report to your pull requests showing whether your pull requests and coverage are up to standards or not as configured on the [quality gate rules](../../repositories-configure/adjusting-quality-gates.md) for your repository. You can then optionally [block merging pull requests that aren't up to standards](../../getting-started/integrating-codacy-with-your-git-workflow.md#blocking-pull-requests). +!!! important + For open source repositories on GitHub, Codacy will not run analysis if **Status checks** is disabled. Make sure this setting is enabled to keep analysis running. + {% include-markdown "../../assets/includes/status-checks-important.md" %} ![Pull request status check on GitHub](images/github-integration-pr-status.png) From a92d2d6a3ff3e33de13990902118f5aa75ec09e6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= Date: Fri, 24 Apr 2026 11:51:43 +0100 Subject: [PATCH 3/4] revert: exclude release notes changes from this PR Co-Authored-By: Claude Sonnet 4.6 --- ...-03-github-integration-settings-changes.md | 25 ++++++------------- 1 file changed, 7 insertions(+), 18 deletions(-) diff --git a/docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md b/docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md index 917b84c0fa..c827ce5838 100644 --- a/docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md +++ b/docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md @@ -9,38 +9,27 @@ rss_href: /feed_rss_created.xml We are making two changes to the GitHub integration settings over the coming weeks. Both are handled automatically - you don't need to take any action. -- [**AI-enhanced comments (Beta) being deprecated for GitHub**](#ai-enhanced-comments) — AI-enhanced comments are being replaced by the [AI Reviewer](../../codacy-ai/codacy-ai.md#pr-reviewer) on March 17, 2026. +- [**AI-enhanced comments (Beta) being deprecated for GitHub**](#ai-enhanced-comments) — AI-enhanced comments are being replaced by the AI Reviewer on March 16, 2026. - [**Coverage summary moving to Pull request review**](#coverage-summary) — the Coverage summary setting is being removed; coverage data will soon be included in the Pull request review comment. -## AI-enhanced comments (Beta) being deprecated on March 17, 2026 {: id="ai-enhanced-comments"} +## AI-enhanced comments (Beta) being deprecated on March 16, 2026 {: id="ai-enhanced-comments"} -Codacy is deprecating the AI-enhanced comments (Beta) feature in favour of the [AI Reviewer](../../codacy-ai/codacy-ai.md#ai-reviewer), which provides a more accurate, comprehensive, and context-aware experience for identifying and addressing issues. - -On March 17, 2026, Codacy will migrate all repositories and organizations that have **AI-enhanced comments** enabled to the [AI Reviewer](../../codacy-ai/codacy-ai.md#ai-reviewer) and remove the setting. +Codacy is deprecating the AI-enhanced comments (Beta) feature in favour of the AI Reviewer, which provides a more accurate, comprehensive, and streamlined experience for identifying and addressing issues. +On March 16, 2026, Codacy will migrate all repositories and organizations that have **AI-enhanced comments** enabled to the AI Reviewer and remove the setting. !!! note Organizations with contractual restrictions on AI providers or content analysis scope will not be automatically migrated to the AI Reviewer. For these organizations, AI-enhanced comments will simply be disabled. The AI Reviewer can be enabled at any time from your [integration settings](../../repositories-configure/integrations/github-integration.md#ai-reviewer). For more information, contact your account manager or . ### What to expect -- On March 17, 2026, the AI-enhanced comments setting will be removed and any repository or organization where it is enabled will be migrated to the AI Reviewer. -- Repositories where AI-enhanced comments are not enabled will not have the AI Reviewer enabled automatically. +- The AI-enhanced comments (Beta) setting will be removed on March 16, 2026. +- If you had AI-enhanced comments enabled at repository or organization level, those will be migrated to the AI Reviewer accordingly. - The AI Reviewer defaults to **manual** mode, so your team won't receive unexpected reviews. ### What do you need to do? -Nothing is required. Codacy will handle the migration automatically. - -If you prefer, you can enable the AI Reviewer now in your organization and repository integration settings. If you enable it before March 17, 2026, we recommend manually disabling **AI-enhanced comments** at the same time to avoid duplicate comments on Pull Requests. - -If you have any further questions, contact . - -### Why this change - -- The [AI Reviewer](../../codacy-ai/codacy-ai.md#pr-reviewer) uses broader context from source code and PR metadata (and Jira tickets, if enabled), which improves accuracy and reduces noise. -- You can guide reviews with custom instructions using a `review.md` file in your repository. -- You can trigger reviews on demand from Pull Requests using the **Run review** button. +Nothing. Codacy will handle the migration automatically. If you have any further questions, contact . ## Coverage summary moving to Pull request review {: id="coverage-summary"} From 6900b0f133bba5b9bcaa529f329c180de9db01d7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia?= <83641264+claudiacodacy@users.noreply.github.com> Date: Fri, 24 Apr 2026 11:55:01 +0100 Subject: [PATCH 4/4] Update docs/faq/troubleshooting/why-isnt-my-public-repository-being-analyzed.md Co-authored-by: codacy-production[bot] <61871480+codacy-production[bot]@users.noreply.github.com> --- .../why-isnt-my-public-repository-being-analyzed.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/faq/troubleshooting/why-isnt-my-public-repository-being-analyzed.md b/docs/faq/troubleshooting/why-isnt-my-public-repository-being-analyzed.md index 8f79619acd..de38e93588 100644 --- a/docs/faq/troubleshooting/why-isnt-my-public-repository-being-analyzed.md +++ b/docs/faq/troubleshooting/why-isnt-my-public-repository-being-analyzed.md @@ -1,8 +1,8 @@ # Why isn't my public repository being analyzed? -Codacy only analyzes open source repositories on GitHub if both of the following conditions are met: +Codacy only analyzes open source repositories if the following conditions are met: - The admin of the repository is a committer to that repository. -- **Status checks** is enabled in the [GitHub integration settings](../../repositories-configure/integrations/github-integration.md#status-checks) for the repository, either directly or via the [organization defaults](../../organizations/integrations/default-git-provider-integration-settings.md). +- For GitHub repositories, **Status checks** is enabled in the [GitHub integration settings](../../repositories-configure/integrations/github-integration.md#status-checks) for the repository, either directly or via the [organization defaults](../../organizations/integrations/default-git-provider-integration-settings.md). If **Status checks** is disabled, Codacy will not run analysis for open source repositories on GitHub.