docs: document automatic removal on GitHub repository archive TAROT-3757#2697
Conversation
Archived repositories are read-only and don't need further analysis, so since July 7, 2026 Codacy automatically removes them from Codacy when they're archived on GitHub. Documents the new section in managing-repositories.md and the corresponding table column in what-are-organizations.md, following the same pattern already used for the repository-transfer cleanup feature (TAROT-3749). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Overall readability score: 54.29 (🔴 -0.01)
View detailed metrics🟢 - Shows an increase in readability
Averages:
View metric targets
|
Up to standards ✅🟢 Issues
|
There was a problem hiding this comment.
Code Review
This pull request updates the documentation to reflect that archiving a repository on GitHub Cloud or GitHub Enterprise Cloud automatically removes it from Codacy starting July 7, 2026. The feedback suggests minor grammatical improvements to avoid word repetition in the new section and to fix a sentence fragment in the updated feature support table footnote.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
Pull Request Overview
This documentation update correctly captures the new automated repository removal behavior for archived GitHub Cloud and GitHub Enterprise Cloud repositories, effective July 7, 2026. The changes include the necessary provider constraints and operational details (e.g., manual re-addition after unarchiving).
Codacy analysis indicates the PR is up to standards with no new quality issues. There are no security flaws or major logic bugs that should prevent merging.
Test suggestions
- Found recommended test scenario: Verify the 'Repository archived on GitHub' section exists in managing-repositories.md with correct constraints on providers and the July 7, 2026 date.
- Found recommended test scenario: Verify the 'Archive repository' column in what-are-organizations.md reflects 'Yes**' for GitHub Cloud and 'No' for GitLab/Bitbucket/GitHub Enterprise (Server).
- Found recommended test scenario: Verify the foot-note (**) in what-are-organizations.md correctly links to the new documentation section and mentions GitHub Enterprise Cloud support.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
Avoid repeating "since" with two different meanings in the same sentence, and fix a sentence fragment in the table footnote. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Summary
organizations/managing-repositories.md(new section) and the provider-support table inorganizations/what-are-organizations.md, following the same pattern used for the repository-transfer cleanup feature (TAROT-3749, PR docs: document automatic cleanup on GitHub repository transfer TAROT-3749 #2696).Jira: https://codacy.atlassian.net/browse/TAROT-3757
Preview
https://tarot-3757-archived-repository-clea--docs-codacy.netlify.app
Pages updated:
Test plan