docs: document automatic cleanup on GitHub repository transfer TAROT-3749

[jorgebraz]

Summary

• GitHub only sends the transferred webhook event to the destination organization when a repository moves between organizations, so Codacy previously had no way to detect and clean it up from the original organization.
• Codacy now automatically removes the repository from the original organization when both the original and destination GitHub organizations are added to Codacy. The destination organization doesn't need a paid plan or any repositories added — just the Codacy GitHub App installed (common for a dedicated "archive" org).
• Documents this in organizations/managing-repositories.md (new section) and the provider-support table in organizations/what-are-organizations.md.

Jira: https://codacy.atlassian.net/browse/TAROT-3749

Preview

https://tarot-3749-repository-transfer-clea--docs-codacy.netlify.app

Pages updated:

• Managing repositories → Transferring a repository to another organization (new section)
• What are organizations → Updates on the Git provider (new table column + note)

Test plan

• Verified all new internal links/anchors resolve to existing files and section ids
• Check the preview links above to confirm rendering

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[github-actions]

Overall readability score: 54.3 (🟢 +0.04)

File	Readability
what-are-organizations.md	48.49 (🔴 -1.7)
managing-repositories.md	54.21 (🔴 -3.97)

View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File	Readability	FRE	GF	ARI	CLI	DCRS
what-are-organizations.md	48.49	20.68	10.68	14.1	14.73	6.86
	🔴 -1.7	🔴 -0.31	🔴 -0.02	🔴 -0.6	🔴 -0.46	🔴 -0.03
managing-repositories.md	54.21	26.1	10.31	13.8	13.23	6.35
	🔴 -3.97	🔴 -0.91	🔴 -0.42	🔴 -1.2	🔴 -0.87	🔴 -0.04

Averages:

	Readability	FRE	GF	ARI	CLI	DCRS
Average	54.3	43.3	10.89	12.3	12.24	8.01
	🟢 +0.04	🟢 +0.12	🟢 +0.01	🟢 +0	🟢 +0	🟢 +0

View metric targets

Metric	Range	Ideal score
Flesch Reading Ease	100 (very easy read) to 0 (extremely difficult read)	60
Gunning Fog	6 (very easy read) to 17 (extremely difficult read)	8 or less
Auto. Read. Index	6 (very easy read) to 14 (extremely difficult read)	8 or less
Coleman Liau Index	6 (very easy read) to 17 (extremely difficult read)	8 or less
Dale-Chall Readability	4.9 (very easy read) to 9.9 (extremely difficult read)	6.9 or less

[gemini-code-assist]

Code Review

This pull request updates the documentation to describe how Codacy automatically handles repository transfers between organizations on GitHub when both the original and destination organizations are added to Codacy. The review feedback points out a logical error in two files where the text incorrectly references the 'original' organization instead of the 'destination' organization as the condition for automatic detection failure, providing suggestions to correct this.

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.

[codacy-production]

Pull Request Overview

While the PR successfully documents the new automated cleanup feature for GitHub repository transfers, there are logical inconsistencies that could mislead users. The documentation currently states that the 'original' organization must be integrated for cleanup to work; however, since the repository already exists in Codacy under that organization, the real requirement for the automation is that the 'destination' organization is integrated to receive the GitHub transfer webhook. Furthermore, the Git provider support table incorrectly lists GitHub Enterprise (on-premises) as a supported platform for this automation, whereas it is restricted to GitHub Cloud and GitHub Enterprise Cloud. Codacy analysis indicates the PR is otherwise up to standards with no new quality issues reported.

About this PR

• The documentation consistently refers to the 'original' organization as the integration requirement for automated cleanup. However, the automated logic relies on the destination organization receiving the 'transferred' event. If the original organization wasn't already in Codacy, the repository wouldn't exist to be cleaned up. The 'failure to detect' logic should focus on whether the destination organization is added.

Test suggestions

• Verify documentation specifies the 'both organizations' requirement for GitHub transfers.
• Verify documentation clarifies that repositories are not automatically added to the destination.
• Verify the provider support table correctly highlights GitHub-only support for this automation.
• Verify internal links between FAQ and organization management pages are correct and use existing anchors.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}