Transferring a Repository

Transferring a Repository

Valuable code and data should be brought into the organisation before you graduate or leave, so that it remains available to future students and researchers. First agree with your supervisor on what is valuable. Then use one of the two methods below.

Method 1: Transfer through GitHub

Best when the repository already lives on your personal account and you want to move it wholesale, keeping its issues, history and stars.

1. Open the repository on GitHub and go to Settings.
2. Scroll to the Danger Zone and choose Transfer.
3. Enter uct-eee-department as the new owner and confirm.

You need permission to create repositories in the organisation. If the transfer option is blocked, ask an administrator. See the GitHub documentation on transferring a repository for detail.

Method 2: Push to a new organisation remote

Best when you want to keep your personal copy and also place a copy in the organisation.

cd /path/to/your/repo
gh repo create uct-eee-department/REPO_NAME --source . --remote uct --private --push

This creates the repository in the organisation and pushes your current code to it. When working with more than one remote, remember to push to each:

git push origin && git push uct

After transferring

• Add or update the README.md, and a LICENSE if the repository will be public.
• Archive the repository if the work is complete, so that it is read-only and clearly finished.
• If you want to keep working on it independently, fork it back to your personal account.