Skip to content

Commit f45d7bf

Browse files
jorgebrazclaude
andauthored
docs: document automatic removal on GitHub repository archive TAROT-3757 (#2697)
* docs: document automatic removal on GitHub repository archive TAROT-3757 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> * docs: fix wording nits from review TAROT-3757 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> --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
1 parent 8be27f8 commit f45d7bf

2 files changed

Lines changed: 22 additions & 8 deletions

File tree

docs/organizations/managing-repositories.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,18 @@ Codacy automatically removes the repository from its original organization when
8888
!!! important
8989
This is currently supported for **GitHub Cloud** and **GitHub Enterprise Cloud** only. For GitLab and Bitbucket, or if the destination organization isn't added to Codacy, [remove the repository manually](../repositories-configure/removing-your-repository.md).
9090

91+
## Repository archived on GitHub {: id="archived-repository"}
92+
93+
Since July 7, 2026, when you archive a repository on GitHub, Codacy automatically removes that repository from Codacy, as archived repositories are read-only and don't need further code quality analysis.
94+
95+
!!! note
96+
This only applies to repositories archived on **GitHub Cloud** or **GitHub Enterprise Cloud** — GitLab and Bitbucket aren't affected.
97+
98+
!!! important
99+
This only applies going forward: repositories that were already archived on GitHub before July 7, 2026 aren't automatically removed. [Remove them manually](../repositories-configure/removing-your-repository.md) if needed.
100+
101+
If you unarchive a repository after Codacy removes it, Codacy doesn't automatically bring it back — you need to [add it back to Codacy](#adding-a-repository) to resume analyzing it.
102+
91103
## Finding your repositories with Segments {: id="provider-segments"}
92104

93105
Codacy allows you to utilise [**Segments**](../segments) to categorize and filter repositories more effectively within the Codacy platform.

docs/organizations/what-are-organizations.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -31,18 +31,20 @@ If you update your organization or repository information on your Git provider,
3131
!!! note
3232
If an update to your organization name isn't automatically reflected on Codacy, navigate to the organization **Settings** page, tab **Profile**, and click the **Synchronize** button.
3333

34-
| Git provider | Rename repository | Change repository visibility | Delete repository | Rename organization or group | Remove member from organization or group | Delete organization or group | Transfer repository to a different organization |
35-
|---|---|---|---|---|---|---|---|
36-
| GitHub Cloud | Yes | Yes | Yes | Yes | Yes | Yes | Yes* |
37-
| GitHub Enterprise | Yes | Yes | Yes | Yes | Yes | Yes | No |
38-
| GitLab Cloud | No | No | No | No | No | No | No |
39-
| GitLab Enterprise | Yes | Yes | Yes | Yes | Yes | Yes | No |
40-
| Bitbucket Cloud | Yes | Yes | No | No | No | No | No |
41-
| Bitbucket Server | Yes | Yes | No | No | No | No | No |
34+
| Git provider | Rename repository | Change repository visibility | Delete repository | Rename organization or group | Remove member from organization or group | Delete organization or group | Transfer repository to a different organization | Archive repository |
35+
|---|---|---|---|---|---|---|---|---|
36+
| GitHub Cloud | Yes | Yes | Yes | Yes | Yes | Yes | Yes* | Yes** |
37+
| GitHub Enterprise | Yes | Yes | Yes | Yes | Yes | Yes | No | No |
38+
| GitLab Cloud | No | No | No | No | No | No | No | No |
39+
| GitLab Enterprise | Yes | Yes | Yes | Yes | Yes | Yes | No | No |
40+
| Bitbucket Cloud | Yes | Yes | No | No | No | No | No | No |
41+
| Bitbucket Server | Yes | Yes | No | No | No | No | No | No |
4242

4343
!!! note
4444
\* Only for GitHub Cloud, including organizations added through GitHub Enterprise Cloud, and only when both the original and destination organizations are added to Codacy. See [Transferring a repository to another organization](managing-repositories.md#transferring-repository).
4545

46+
\*\* Since July 7, 2026, Codacy automatically removes repositories archived on GitHub Cloud (including GitHub Enterprise Cloud) from Codacy. See [Repository archived on GitHub](managing-repositories.md#archived-repository).
47+
4648
See also the [roles and permission mapping from the Git providers](roles-and-permissions-for-organizations.md).
4749

4850
## Deleting an organization

0 commit comments

Comments
 (0)