From e70cbe7ece51c6bcd785c32ebf09a531e8fac7ac Mon Sep 17 00:00:00 2001 From: Jorge Braz Date: Tue, 7 Jul 2026 17:28:17 +0100 Subject: [PATCH 1/2] 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 --- docs/organizations/managing-repositories.md | 12 ++++++++++++ docs/organizations/what-are-organizations.md | 18 ++++++++++-------- 2 files changed, 22 insertions(+), 8 deletions(-) diff --git a/docs/organizations/managing-repositories.md b/docs/organizations/managing-repositories.md index 9ab047c3e7..663e404569 100644 --- a/docs/organizations/managing-repositories.md +++ b/docs/organizations/managing-repositories.md @@ -88,6 +88,18 @@ Codacy automatically removes the repository from its original organization when !!! important 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). +## Repository archived on GitHub {: id="archived-repository"} + +Since July 7, 2026, when you archive a repository on GitHub, Codacy automatically removes that repository from Codacy, since archived repositories are read-only and don't need further code quality analysis. + +!!! note + This only applies to repositories archived on **GitHub Cloud** or **GitHub Enterprise Cloud** — GitLab and Bitbucket aren't affected. + +!!! important + 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. + + 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. + ## Finding your repositories with Segments {: id="provider-segments"} Codacy allows you to utilise [**Segments**](../segments) to categorize and filter repositories more effectively within the Codacy platform. diff --git a/docs/organizations/what-are-organizations.md b/docs/organizations/what-are-organizations.md index 28b2f2aa87..ec4dd9da96 100644 --- a/docs/organizations/what-are-organizations.md +++ b/docs/organizations/what-are-organizations.md @@ -31,18 +31,20 @@ If you update your organization or repository information on your Git provider, !!! note 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. -| 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 | -|---|---|---|---|---|---|---|---| -| GitHub Cloud | Yes | Yes | Yes | Yes | Yes | Yes | Yes* | -| GitHub Enterprise | Yes | Yes | Yes | Yes | Yes | Yes | No | -| GitLab Cloud | No | No | No | No | No | No | No | -| GitLab Enterprise | Yes | Yes | Yes | Yes | Yes | Yes | No | -| Bitbucket Cloud | Yes | Yes | No | No | No | No | No | -| Bitbucket Server | Yes | Yes | No | No | No | No | No | +| 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 | +|---|---|---|---|---|---|---|---|---| +| GitHub Cloud | Yes | Yes | Yes | Yes | Yes | Yes | Yes* | Yes** | +| GitHub Enterprise | Yes | Yes | Yes | Yes | Yes | Yes | No | No | +| GitLab Cloud | No | No | No | No | No | No | No | No | +| GitLab Enterprise | Yes | Yes | Yes | Yes | Yes | Yes | No | No | +| Bitbucket Cloud | Yes | Yes | No | No | No | No | No | No | +| Bitbucket Server | Yes | Yes | No | No | No | No | No | No | !!! note \* 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). + \*\* Codacy automatically removes the repository from Codacy. Since July 7, 2026, and only for repositories archived on GitHub Cloud (including GitHub Enterprise Cloud). See [Repository archived on GitHub](managing-repositories.md#archived-repository). + See also the [roles and permission mapping from the Git providers](roles-and-permissions-for-organizations.md). ## Deleting an organization From b7612682c2810b646b2078e2e09a920c2590eefe Mon Sep 17 00:00:00 2001 From: Jorge Braz Date: Tue, 7 Jul 2026 17:35:00 +0100 Subject: [PATCH 2/2] 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 --- docs/organizations/managing-repositories.md | 2 +- docs/organizations/what-are-organizations.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/organizations/managing-repositories.md b/docs/organizations/managing-repositories.md index 663e404569..0d5970054c 100644 --- a/docs/organizations/managing-repositories.md +++ b/docs/organizations/managing-repositories.md @@ -90,7 +90,7 @@ Codacy automatically removes the repository from its original organization when ## Repository archived on GitHub {: id="archived-repository"} -Since July 7, 2026, when you archive a repository on GitHub, Codacy automatically removes that repository from Codacy, since archived repositories are read-only and don't need further code quality analysis. +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. !!! note This only applies to repositories archived on **GitHub Cloud** or **GitHub Enterprise Cloud** — GitLab and Bitbucket aren't affected. diff --git a/docs/organizations/what-are-organizations.md b/docs/organizations/what-are-organizations.md index ec4dd9da96..a056b9f777 100644 --- a/docs/organizations/what-are-organizations.md +++ b/docs/organizations/what-are-organizations.md @@ -43,7 +43,7 @@ If you update your organization or repository information on your Git provider, !!! note \* 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). - \*\* Codacy automatically removes the repository from Codacy. Since July 7, 2026, and only for repositories archived on GitHub Cloud (including GitHub Enterprise Cloud). See [Repository archived on GitHub](managing-repositories.md#archived-repository). + \*\* 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). See also the [roles and permission mapping from the Git providers](roles-and-permissions-for-organizations.md).