This article describes the process for users to migrate their personally owned repositories from github.ncsu.edu to the GitHub Enterprise Cloud service.
The on-prem GitHub service is being retired in favor of new GitHub Enterprise Cloud service. Users are required to migrate their data to the Cloud service by 2025-12-20.
To migrate repositories from an organization, please refer to the organization migration KB article.
Please review the following material before starting your migration process:
- GitHub Enterprise Cloud Service Policies
- Differences between the github.ncsu.edu and GitHub Enterprise Cloud services
- Logging in to GitHub Enterprise Cloud
To migrate user owned repositories, it is recommended to use the Importer Tool in the GitHub web interface.
Note that Issues, Pull Requests, Wikis, etc, will NOT be included in the migration. In cases where these are critical to keep, the repository likely holds significance to university business and should be owned by an organization. Therefore it is recommended to transfer the repository to an organization on github.ncsu.edu, and then follow the steps for migrating repositories owned by an organization as documented below.
For more information on using the Importer tool, see the official GitHub documentation here: https://docs.github.com/en/enterprise-cloud@latest/migrations/importing-source-code/using-github-importer/importing-a-repository-with-github-importer
Be sure to use the HTTPS URL for your repository, as the importer tool cannot use the SSH URL.
For the password field, you will need to create a classic Personal Access Token (PAT) for your account with the full "repo" permission enabled, and use the PAT as the password.
Once the migration has finished, you should check the migrated repository in GitHub Enterprise Cloud to ensure that everything migrated successfully.
You should see the full git history of the repository in the Code view.
If other users need access to the repository, assign permissions to those users appropriate.
Test that you and any collaborators are able to successfully access and clone the repository.
If you have any local copies of the repository, you'll want to update the origin URL to point to the new repository.
git remote set-url origin <HTTPS/SSH URL>You may need to update references in your IDE, scripts and automation, configuration files, etc.
Ensure that everything is using the new repository correctly.
To finalize the migration, you should remove the old repository on github.ncsu.edu. This ensures that no one attempts to read or update the old repository.