Repository transfer

[nmanriqueb2609]

Select Topic Area

Question

Body

Hi, is it possible to transfer repositories from a personal account to an organization without having permission to create repositories in the organization? If not, what other way can it be done? Perhaps transfer to the administrator account, and then transfer them to the organization?

[Aqib121201]

You can’t transfer a repository to an organization unless your account has permission to create repos there. That’s a built-in restriction to prevent users from adding projects without approval.

The easiest way around it is to ask an admin in the organization to temporarily grant you repo creation rights. Once you finish the transfer, they can remove that permission again.

If that’s not possible, you can transfer the repo to an admin’s personal account first. The admin can then move it from their account into the organization. Just keep in mind that every transfer step will require confirmation from both sides.

If this cleared things up, please mark the answer as helpful so others can find it easily.

[randomcat962codes]

You might be able to send someone the source code of the repository and they can create a new repository under the organization, and you can just mark your original repo as private or delete it.

[NTHoang2103]

1. Requirements for Transfer
   Before starting the transfer, make sure both parties meet these conditions:

Original Owner: Must have admin access to the repository.

Recipient (New Owner): Must explicitly accept the transfer.

Permissions: The recipient must be a collaborator on the repository or, if the transfer is to an Organization, a member of that Organization with permission to create repositories.

Repository Size: The repository must not exceed GitHub's size limits.

2. Steps to Initiate the Transfer
   This process is initiated by the current owner via the GitHub web interface:

Navigate to the Repository: Go to the main page of the repository you want to transfer.

Access Settings: Click on the Settings tab.

Find the Transfer Section: Scroll down to the bottom of the page to the "Danger Zone" section.

Start the Transfer:

Click the "Transfer" button.

In the pop-up window, you will be asked to confirm your account password for security.

Specify the New Owner:

In the "Transfer to" field, type the username or organization name of the new owner. GitHub will show a warning if the repository visibility will change (e.g., transferring a private repo to an organization that only allows public repos).

Click "I understand, transfer this repository."

3. Steps for the Recipient to Accept
   If the repository is transferred to a personal user, the recipient will receive an email and a notification on GitHub:

Check Email/Notifications: The recipient will receive an email asking them to accept the transfer.

Accept the Transfer: They must click the link in the email or the notification on GitHub to accept the transfer of ownership.

Important Considerations After Transfer
URL Change: The repository's URL will immediately change to reflect the new owner (github.com/new-owner/repo-name).

Local Clones: Just like renaming, anyone with a local clone must update their remote URL to point to the new owner's address.

Bash

git remote set-url origin https://github.com/<NEW_OWNER_NAME>/<REPO_NAME>.git
Permissions and Access: All collaborators on the repository will retain access, but their permissions may change depending on the new owner's settings (especially if transferred to an Organization).

Integrations: Any webhooks, deployment keys, or integrations (like CI/CD services) set up on the old repository will break and must be reconfigured by the new owner.

Redirects: GitHub does not automatically redirect traffic from the old owner's URL (old-owner/repo-name) to the new owner's URL (new-owner/repo-name).

[Ravi-GitLab-7]

You can’t transfer a repository to an organization unless your account has permission to create repos there. That’s a built-in restriction to prevent users from adding projects without approval.

The easiest way around it is to ask an admin in the organization to temporarily grant you repo creation rights. Once you finish the transfer, they can remove that permission again.

If that’s not possible, you can transfer the repo to an admin’s personal account first. The admin can then move it from their account into the organization. Just keep in mind that every transfer step will require confirmation from both sides.

If this cleared things up, please mark the answer as helpful so others can find it easily.