Skip to content

chore: update date + context to match email #2605

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
claudiacodacy merged 1 commit into from
Mar 3, 2026
Merged

chore: update date + context to match email #2605

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 18 additions & 7 deletions docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,27 +9,38 @@

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.

Check failure on line 12 in docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Microsoft.Dashes] Remove the spaces around ' — '.

Raw Output:
{"message": "[Microsoft.Dashes] Remove the spaces around ' — '.", "location": {"path": "docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md", "range": {"start": {"line": 12, "column": 89}}}, "severity": "ERROR"}
- [**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.
Comment on lines +17 to +19
Copy link
Contributor

@codacy-production codacy-production bot Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ LOW RISK

The links to the AI Reviewer documentation are inconsistent. Lines 17 and 19 use the anchor #ai-reviewer, while lines 12, 41, and the file footer use #pr-reviewer.

This might be a simple fix:

Suggested change
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](../../codacy-ai/codacy-ai.md#pr-reviewer), which provides a more accurate, comprehensive, and context-aware 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.
- 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.

Check failure on line 27 in docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'it's' instead of 'it is'.

Raw Output:
{"message": "[Microsoft.Contractions] Use 'it's' instead of 'it is'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md", "range": {"start": {"line": 27, "column": 114}}}, "severity": "ERROR"}
- Repositories where AI-enhanced comments are not enabled will not have the AI Reviewer enabled automatically.

Check failure on line 28 in docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'won't' instead of 'will not'.

Raw Output:
{"message": "[Microsoft.Contractions] Use 'won't' instead of 'will not'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md", "range": {"start": {"line": 28, "column": 61}}}, "severity": "ERROR"}

Check failure on line 28 in docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'aren't' instead of 'are not'.

Raw Output:
{"message": "[Microsoft.Contractions] Use 'aren't' instead of 'are not'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md", "range": {"start": {"line": 28, "column": 45}}}, "severity": "ERROR"}
- 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>.
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 <support@codacy.com>.

### 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"}

Expand Down
Loading