Transferring a Repository to an Organisationο
π’ This guide explains how to transfer a GitHub repository from a personal account to an organisation. While not required, this can help promote collaborative ownership and reduce barriers to contribution.
π¦ Why Transfer to an Organisation?ο
Enables team-based permissions
Reduces visibility of individual ownership
Simplifies future collaboration and maintenance
You might want to transfer if youβre planning broader community involvement, long-term support, or a publication release.
π Steps for Transferring a Repositoryο
1. Prepare an Organisation and Teamο
Make sure youβre an admin of the destination GitHub organisation.
Create a team for maintainers (e.g.,
ifmeo-hamburg/seagliderOG1-maintainers).
2. Transfer the Repositoryο
Go to Settings in your GitHub repo.
Scroll to Danger Zone and click Transfer Ownership.
Enter the organisation name and confirm.
3. Verify the Moveο
Go to the new repository URL under the organisation.
Check that all content moved:
Issues
Pull requests
Branch protection rules
4. Reassign Rolesο
Visit Settings > Collaborators and Teams.
Ensure team members have appropriate roles (e.g., βWriteβ or βMaintainβ).
5. Notify Collaboratorsο
Let team members and contributors know the repo has moved.
βοΈ Post-Transfer Clean-upο
π Update Linksο
[ ] Update all internal links to the repo in:
README.mddocs/index.rstdocs/source/conf.pyCitation files (e.g.
CITATION.cffβurl:field)
π PyPI and Trusted Publisher (Later Step)ο
[ ] In PyPI settings, update the GitHub repository address.
[ ] Reconfigure trusted publisher settings for the new repo path.
π Conda-forge (Later Step)ο
[ ] If distributing via conda-forge, update
meta.yamlto match the new repo location.
π pyproject.tomlο
[ ] Update
urls.repositoryandurls.documentationto the new GitHub URL.
π€ Final Step for Original Ownerο
If the repo started under your personal account (e.g., github.com/eleanorfrajka/seagliderOG1) and you want to keep working on it:
Fork the new repo from the organisation to your personal GitHub account.
β After transfer and cleanup, your repository is easier to maintain as a team project and better prepared for citation, publishing, and long-term support.