Preserving high-traffic repository URL when migrating a personal account to an organization #213373
Replies: 3 comments 1 reply
|
Hello! This is an important migration to plan carefully, especially given the repository's traffic. I checked GitHub's current documentation, and there's one significant risk in the proposed procedure. 1. Namespace retirement is the main concern GitHub's [repository transfer documentation](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository) and [username reference](https://docs.github.com/en/account-and-profile/reference/username-reference) both describe permanent retirement of an exact Your reported 985 clones over 14 days make this particularly important. However, the relevant measurement is the preceding seven-day period, not the 14-day total. 2. Recreating the original path may not be possible The documentation explicitly states that a retired repository namespace cannot be reused. Therefore, I would not assume that creating an organization with the original username will make The retirement applies to the exact owner/repository combination, not simply to the username. 3. A temporary organization may not solve this Transferring the repository to a temporary organization first is not necessarily safer. Repository transfers themselves can trigger namespace retirement when the documented thresholds are met. Changing the order of operations does not provide a documented way around that restriction. 4. Additional migration considerations A few things worth checking before proceeding:
GitHub generally redirects repository references after transfers, but redirects should not be treated as a substitute for preserving the original namespace. Also, GitHub warns that creating a new repository or fork at a previous location can permanently remove existing redirects. My recommendation: Do not rename the personal account or initiate any repository transfers yet. First, verify the clone and Actions usage for the exact preceding seven-day period and obtain written clarification from GitHub Support about this specific migration. The critical question to get answered is: Can GitHub preserve or explicitly authorize the reuse of the exact Since the repository is already widely used in research pipelines, I would prioritize preserving the existing URL over rushing the governance migration. Hope this helps clarify the risk before you make an irreversible change! |
|
Thank you for the clarification. I checked GitHub's updated documentation, and there is an important distinction between preserving the organization username and preserving the exact repository namespace. As of January 12, 2026, GitHub has deprecated direct personal-account-to-organization conversion. The supported approach is now to rename the personal account, create an organization using the original username, and move the repositories to that organization. However, this does not eliminate the repository namespace retirement risk. According to GitHub's documentation, a public repository with more than 100 clones or more than 100 GitHub Actions uses during the preceding week can have its original Regarding your questions:
My recommendation would be to keep the existing account and repositories unchanged until GitHub Support provides an account-specific answer. I would specifically ask GitHub whether they can facilitate the migration while preserving both the original organization username and the exact repository namespace, despite the repository's traffic statistics. Since scientific publications and external research pipelines depend on these URLs, preserving long-term compatibility should take priority over completing the migration quickly. Hope this helps! |
|
Hi, I'm not GitHub staff, but your situation matches a documented rule and at least one community report, so here is my reading. 1. Namespace retirement: your main repository probably qualifies GitHub's documentation on changing your username says that when you rename an account, GitHub permanently retires the old
With 985 clones in 14 days (178 unique cloners), your main repository is likely above 100 clones in a typical week, so I'd assume Questions 1 and 2, based on a similar case Discussion #211038 describes someone who followed the documented "rename the personal account, create an organization with the old name, transfer the repository" procedure and was then told the path was retired when they tried to transfer. That is the same sequence you plan. I don't know of a documented self-service way to reuse a retired path, even for the organization that now holds the same name, and I can't tell you whether GitHub staff can lift a retirement. I'd treat it as unavailable unless GitHub says otherwise in writing. 2. A possible way to avoid the rename completely (verify first) GitHub documents converting a personal account into an organization (in the docs: "Converting a user into an organization", under the account settings, in the Organizations area). As I understand it, this keeps the same name and leaves the repositories in place, so
Test the process on a throwaway account with a similar setup first. 3. Question 4: a temporary organization Transferring to a temporary organization and renaming it later probably doesn't help, because a path is retired when the owner name changes, and an organization rename is a change of owner name too. I haven't confirmed this for organizations, so ask GitHub. If you do use any rename-based route, don't leave the freed name unclaimed. Claim it right away, because an unclaimed old name is exactly what retirement protects against (repo hijacking). 4. Question 5: integrations and the fork
5. Getting a firm answer Because the cost of a wrong move is high and some of it is irreversible, I'd ask GitHub Support again with two precise questions, in writing:
Quote the namespace retirement paragraph from the username documentation, state the traffic numbers, and reference ticket #5018756. Don't rename or transfer anything until you have an answer you trust, which is what you've already decided to do. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
Body
Hello GitHub Community,
We maintain OrthoFinder, a widely used open-source bioinformatics project.
We would like to migrate our existing personal GitHub account (
OrthoFinder) into a GitHub organization using the same name. Our goal is to allow multiple researchers to independently administer their own repositories while maintaining a shared project identity.However, we are concerned about GitHub's repository namespace retirement policy, particularly because our main repository receives substantial traffic.
1. Proposed migration procedure
According to GitHub's Moving your work to an organization documentation, the recommended procedure for retaining the original username is:
OrthoFindertoOrthoFinder-legacy.OrthoFinder.Our intended final repository address is:
https://github.com/OrthoFinder/OrthoFinder
We need this to remain the actual repository location, rather than merely redirecting to another organization such as
OrthoFinderLab.2. Concern: Permanent repository namespace retirement
GitHub's documentation explains that certain repository paths may be permanently retired when an account is renamed or a repository is transferred.
Our main repository currently has the following traffic statistics:
GitHub's documented namespace retirement conditions include repositories with more than 100 clones in the preceding week, more than 100 GitHub Actions uses in that period, or GitHub Marketplace-listed Actions.
Given our repository's traffic, we are concerned that the existing
OrthoFinder/OrthoFindernamespace may become permanently retired when the personal account is renamed.If that happens, we are unsure whether GitHub will allow the original repository to be transferred back into the same
OWNER/REPOSITORYnamespace under a newly created organization.3. Our questions
Question 1 — Namespace retirement
If we rename the personal account
OrthoFindertoOrthoFinder-legacy, would GitHub permanently retire the originalOrthoFinder/OrthoFinderrepository path because of its high clone traffic?Question 2 — Reusing the exact original path
If the repository path is retired, would GitHub prevent us from transferring the repository into a newly created organization named
OrthoFinder, even though the organization would use the same username as the original personal account?In other words, can a repository namespace retired during a personal-account rename be reused by an organization that subsequently acquires the original username?
Question 3 — Experience with high-traffic repositories
Has anyone successfully migrated a high-traffic public repository from a personal account to an organization with the same name while retaining the exact original
OWNER/REPOSITORYpath?We would particularly appreciate experiences involving repositories that exceeded GitHub's namespace retirement thresholds.
Question 4 — Alternative migration methods
Is there a supported migration procedure, workaround, or coordinated approach that would allow us to preserve the exact repository address without triggering permanent namespace retirement?
Would transferring repositories to a temporary organization first, followed by renaming the organization, make any difference?
Question 5 — External integrations and repository metadata
Our repositories are referenced by:
The main
OrthoFinder/OrthoFinderrepository is also a fork of another public GitHub repository.Are there additional restrictions or precautions concerning these integrations, existing forks, repository redirects, or release URLs when moving from a personal account to an organization?
4. Why preserving the original URL matters
OrthoFinder is an established open-source research tool used internationally.
Changing its repository location could affect external dependencies, installation instructions, automated downloads, and published references.
Although GitHub normally provides redirects after repository transfers, we would prefer to preserve the exact original repository path rather than rely on redirects indefinitely.
Our goal is to improve long-term project governance without disrupting existing researchers or software workflows.
5. Previous contact with GitHub Support
We submitted GitHub Support ticket
#5018756requesting clarification about namespace retirement and the possibility of a coordinated migration.However, our support entitlement is currently limited to self-service resources, and the ticket was closed without an account-specific technical assessment.
We were advised to consult GitHub Community Discussions.
6. What we are hoping to confirm
Before proceeding, we would appreciate clarification on whether the documented migration procedure can safely preserve the exact
OrthoFinder/OrthoFinderrepository address in our situation.In particular, we are looking for guidance on the interaction between:
OWNER/REPOSITORYpath.Any advice from GitHub staff or maintainers who have completed similar migrations would be greatly appreciated.
We have already created and verified local Git backups of seven repositories, and we have not yet renamed or transferred the existing personal account.
Thank you very much for your time and guidance!
The OrthoFinder Project Team
All reactions