codacy · claudiacodacy · Mar 2, 2026 · Mar 2, 2026 · Mar 2, 2026 · Mar 2, 2026
@@ -68,7 +68,7 @@ More details about [False Positives here](../repositories/commits.md#false-posit
 
 _This feature leverages Google Gemini models, and is strictly opt-in: it will only run on repositories or projects where a repository admin has enabled it._
 
-The AI Reviewer combines the reliability of deterministic, rule-based static code analysis with the power of AI. It draws in the necessary context from source code and PR metadata to ensure the business intent matches the technical outcome, and can catch logic gaps that conventional scanners (and human reviewers) often miss.
+The AI Reviewer combines the reliability of deterministic, rule-based static code analysis with the enhanced context and prioritization capabilities of AI. It draws in the necessary context from source code and PR metadata to ensure the business intent matches the technical outcome, and can catch logic gaps that conventional scanners (and human reviewers) often miss.
 
 More details about [AI Reviewer here](../repositories-configure/integrations/github-integration.md#ai-reviewer).
 

@@ -0,0 +1,53 @@
+---
+rss_title: Codacy release notes RSS feed
+rss_href: /feed_rss_created.xml
+---
+
+# Changes to GitHub integration settings – March 2026
+
+!!! info "These changes apply only to GitHub"
+
+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.
+-   [**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"}
+
+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 <support@codacy.com>.
+
+### 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.
+-   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 <support@codacy.com>.
+
+## Coverage summary moving to Pull request review {: id="coverage-summary"}
+
+Codacy is consolidating coverage data into the Pull request review comment so that you get a complete picture of your code quality and security changes in a single place, without the need for a separate comment.
+
+In the coming weeks, Codacy will migrate all repositories and organizations that have **Coverage summary** enabled to **Pull request review**. On that date, the Coverage summary setting will be removed.
+
+### What to expect
+
+-   Coverage changes will appear alongside quality and security metrics in the Codacy Analysis Summary PR comment.
+-   The Coverage summary setting will be removed.
+-   The AI Reviewer is **not** automatically enabled as part of this migration.
+
+### What do you need to do?
+
+Nothing. Codacy will handle the migration automatically for any repository or organization that had Coverage summary enabled. If you didn't have this setting on, this won't affect you.
+
+## See also
+
+-   [GitHub integration](../../repositories-configure/integrations/github-integration.md)
+-   [AI Reviewer](../../codacy-ai/codacy-ai.md#pr-reviewer)
@@ -30,7 +30,7 @@ Adds a report to your pull requests showing whether your pull requests and cover
 
 ![Pull request status check on GitHub](images/github-integration-pr-status.png)
 
-### AI Reviewer
+### Pull request review {: id="pull-request-review"}
 
 {%
     include-markdown "../../assets/includes/paid.md"
@@ -41,17 +41,26 @@ Adds a report to your pull requests showing whether your pull requests and cover
 !!! note
     This feature is only supported on GitHub.
 
-    If you choose to enable the AI Reviewer, consider disabling the AI-enhanced comments, as it may duplicate any comments on Codacy issues you receive.
+When enabled, Codacy posts a **Codacy's Analysis Summary** comment on your pull requests each time a new analysis completes, giving you a full overview of code quality,  security, complexity, and duplication metric changes, without requiring you to open the Codacy app.
 
-The AI Reviewer combines the reliability of deterministic, rule-based static code analysis with the power of AI. It draws in the necessary context from source code and PR metadata to ensure the business intent matches the technical outcome, and can catch logic gaps that conventional scanners (and human reviewers) often miss.
+#### Enable AI reviewer {: id="ai-reviewer"}
+
+!!! note
+    If you enable the AI Reviewer, consider disabling AI-enhanced comments to avoid receiving duplicate comments on Codacy issues.
+
+The AI Reviewer extends Pull request review with an AI-powered code analysis. It combines the reliability of deterministic, rule-based static code analysis with the enhanced context and prioritization capabilities of AI. It draws in the necessary context from source code and PR metadata to ensure the business intent matches the technical outcome, and can catch logic gaps that conventional scanners (and human reviewers) often miss.
 
 It provides feedback on missing or weak tests, complex or duplicated code, and keeps security concerns up to date. Beyond that, it adds contextual insights about whether the changes follow the requirements, business rules, and logic used in the project.
 
-!!! tip
-    Improve the AI Reviewer results by providing custom instructions. [Learn how to do it here](../../codacy-ai/codacy-ai.md#custom-instructions).
+Configure when the AI Reviewer runs using the **Run reviewer** setting:
 
-This setting can be enabled at a repository or organization level. Once enabled, Codacy will start adding a Summary to your pull requests based on the AI-enriched reviews. To request a PR review, click **Run Reviewer** in the Summary or call our [public API](https://api.codacy.com/api/api-docs#triggerpullrequestaireview). Your review will be published as soon as it's ready.
+| Mode | Behaviour |
+|------|-----------|
+| Manually | Click **Run Reviewer** in the pull request comment or call our [public API](https://api.codacy.com/api/api-docs#triggerpullrequestaireview) to trigger a review on demand. |
+| Automatically (first review only) | Codacy runs the reviewer once automatically when the pull request is opened, then requires manual triggering for subsequent updates. |
 
+!!! tip
+    Improve the AI Reviewer results by providing custom instructions. [Learn how to do it here](../../codacy-ai/codacy-ai.md#custom-instructions).
 
 ![AI Reviewer on Github](images/github-integration-ai-reviewer.png)
 
@@ -70,6 +79,9 @@ Shows an overall view of the changes in the pull request, including new issues a
 
 ### Coverage summaries
 
+!!! warning "Coverage summary is moving to Pull request review"
+    In the coming weeks, Codacy will include coverage data in the Pull request review comment and remove the Coverage summary setting. [Learn more](../../release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md#coverage-summary).
+
 Adds a pull request comment showing an overall view of the coverage metrics for the pull request, including details about the data that Codacy used to calculate the coverage variation and diff coverage metrics.
 
 When there are new coverage results, Codacy updates the last coverage summary comment if it's included in the last 5 comments of the pull request. Otherwise, Codacy creates a new comment.
@@ -99,6 +111,9 @@ Adds comments on the lines of the pull request where Codacy finds new issues wit
 
 ### AI-enhanced comments
 
+!!! warning "AI-enhanced comments (Beta) is being deprecated on March 16, 2026"
+    This feature is being replaced by the AI Reviewer, which provides a more accurate and comprehensive experience. [Learn more](../../release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md#ai-enhanced-comments).
+
 Adds AI-enhanced comments, providing insights and ready-to-commit AI-generated fixes for identified issues in cases where tool-suggested fixes are not supported. To enable this option, you must enable **Suggested fixes** first.
 
 {% include-markdown "../../assets/includes/ai-info.md" %}

@@ -690,7 +690,8 @@ nav:
           - release-notes/index.md
           - Cloud:
                 - 2026:
-                      - release-notes/cloud/cloud-2026-01.md  
+                      - release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md
+                      - release-notes/cloud/cloud-2026-01.md
                       - release-notes/cloud/cloud-2026-01-adding-golangci-lint.md
                 - 2025:
                       - release-notes/cloud/cloud-2025-12.md