Preparing the source organization on GitHub
-
Ensure that you have owner permissions on the source organization's repositories.
-
Genera un acceso de token con los alcances
repo
yadmin:org
on GitHub.com. -
Para minimizar los tiempos de inactividad, haz una lista de repositorios que deseas exportar desde la instancia de origen. Puedes agregar múltiples repositorios a una exportación a la vez usando un archivo de texto que muestra la URL de cada repositorio en una línea separada.
Exporting the organization's repositories
Nota: Las relaciones de las bifurcaciones no persisten después de una migración.
To export repository data from GitHub.com, use the Migrations API.
The Migrations API is currently in a preview period, which means that the endpoints and parameters may change in the future.
Generating a migration archive
Nota: El bloquear un repositorio impedirá todos los accesos de escritura al mismo. No puedes asociar equipos o colaboradores nuevos con un repositorio bloqueado. Si estás llevando a cabo una ejecución de prueba, no necesitas bloquear el repositorio. Cuando migras los datos desde un repositorio que está en uso,
GitHub recomienda fuertemente que lo bloquees. Para obtener más información, consulta "Acerca de las migraciones".
-
Notify members of your organization that you'll be performing a migration. The export can take several minutes, depending on the number of repositories being exported. The full migration including import may take several hours so we recommend doing a trial run in order to determine how long the full process will take. For more information, see "About Migrations."
-
Start a migration by sending a
POST
request to the migration endpoint. You'll need:- Your access token for authentication.
- A list of the repositories you want to migrate:
curl -H "Authorization: token GITHUB_ACCESS_TOKEN" \ -X POST \ -H "Accept: application/vnd.github.v3+json" \ -d'{"lock_repositories":true,"repositories":["orgname/reponame", "orgname/reponame"]}' \ https://api.github.com/orgs/orgname/migrations
- If you want to lock the repositories before migrating them, make sure
lock_repositories
is set totrue
. This is highly recommended. - You can exclude file attachments by passing
exclude_attachments: true
to the endpoint. Los archivos adjuntos pueden resultar muy grandes y es posible que sobrecarguen tu archivo de migración final de manera innecesaria. The final archive size must be less than 20 GB.
This request returns a unique
id
which represents your migration. You'll need it for subsequent calls to the Migrations API. -
Send a
GET
request to the migration status endpoint to fetch the status of a migration. You'll need:- Your access token for authentication.
- The unique
id
of the migration:curl -H "Authorization: token GITHUB_ACCESS_TOKEN" \ -H "Accept: application/vnd.github.v3+json" \ https://api.github.com/orgs/orgname/migrations/id
A migration can be in one of the following states:
pending
, which means the migration hasn't started yet.exporting
, which means the migration is in progress.exported
, which means the migration finished successfully.failed
, which means the migration failed.
-
After your migration has exported, download the migration archive by sending a
GET
request to the migration download endpoint. You'll need:- Your access token for authentication.
- The unique
id
of the migration:curl -H "Authorization: token GITHUB_ACCESS_TOKEN" \ -H "Accept: application/vnd.github.v3+json" \ -L -o migration_archive.tar.gz \ https://api.github.com/orgs/orgname/migrations/id/archive
-
The migration archive is automatically deleted after seven days. If you would prefer to delete it sooner, you can send a
DELETE
request to the migration archive delete endpoint. You'll need:- Your access token for authentication.
- The unique
id
of the migration:curl -H "Authorization: token GITHUB_ACCESS_TOKEN" \ -X DELETE \ -H "Accept: application/vnd.github.v3+json" \ https://api.github.com/orgs/orgname/migrations/id/archive
-
Para preparar los datos de migración archivados para importarlos a la instancia de GitHub Enterprise Server, consulta la sección "Prepararse para migrar los datos a tu empresa".