Migrate your repositories from GitLab to GitHub

Prerequisites

• You must have completed all previous phases of this guide.
• The GitLab project must be enabled for exports. See Enable project export and Sidekiq configuration for imports in the GitLab documentation.
• 移行されるデータと、Importer の既知のサポート制限事項を理解していることを確認します。 For more information, see Understand migrations from GitLab to GitHub.
• 必須ではありませんが、運用環境の移行の間は作業を停止することをお勧めします。 Importer は差分移行をサポートしていないため、移行中に発生した変更は移行されません。 運用環境の移行の間に作業を停止しない場合は、これらの変更を手動で移行する必要があります。

Performing a trial run

企業固有の問題を明らかにするために、移行の試用を実行することを強くお勧めします。 試用版の実行では、次の内容について学習します。

• 特定のリポジトリの移行が正常に完了できるかどうか。
• 移行されたリポジトリを実行可能な状態に戻すことができるかどうか。
• 移行の実行にかかる時間。

試用版の実行はいつでも実行でき、移行中に作業を停止する必要はありません。 試験的移行の完了にかかる時間を短縮するには、試験的実行のバッチを連続してスケジュールできます。 それらのリポジトリのユーザーは、都合のよいときに結果を検証できます。

1. Create a test organization for your trial migrations.

   You can use a single organization for all trial runs, or you can create one test organization for each intended destination organization. Consider including -sandbox at the end of the organization names, to clarify that the organizations are intended only for migration validation and not for production. You can delete the test organizations after you're done.

2. Run the trial migrations.

3. Confirm that you are able to complete the follow-up tasks in Follow-up tasks.

4. Ask users to validate the results of the migrations.

5. Resolve any issues uncovered by your trial migrations.

6. 必要に応じて、テスト用の Organization を削除します。

Migrating a single repository

To migrate one repository, use the gh gl2gh migrate-repo command.

gh gl2gh migrate-repo \
  --gitlab-server-url GITLAB_SERVER_URL \
  --gitlab-group SOURCE_GROUP \
  --gitlab-project SOURCE_PROJECT \
  --github-org DESTINATION \
  --github-repo NEW_REPO_NAME \
  --use-github-storage

gh gl2gh migrate-repo \
  --gitlab-server-url GITLAB_SERVER_URL \
  --gitlab-group SOURCE_GROUP \
  --gitlab-project SOURCE_PROJECT \
  --github-org DESTINATION \
  --github-repo NEW_REPO_NAME \
  --use-github-storage

Replace the placeholders in the command above with the following values.

If you are not using GitHub-owned blob storage, see Configure blob storage.

Additional arguments

Generating a migration script

If you want to migrate multiple repositories to GitHub Enterprise Cloud at once, use the GitHub CLI to generate a migration script. The resulting script contains one migrate-repo command per repository.

To generate a migration script, run the gh gl2gh generate-script command.

gh gl2gh generate-script \
  --gitlab-server-url GITLAB_SERVER_URL \
  --github-org DESTINATION \
  --output FILENAME \
  --use-github-storage

gh gl2gh generate-script \
  --gitlab-server-url GITLAB_SERVER_URL \
  --github-org DESTINATION \
  --output FILENAME \
  --use-github-storage

Replace the placeholders in the command above with the following values.

By default, the script includes every project the token can access. To scope the script, add --gitlab-group GROUP, or --gitlab-group GROUP --gitlab-project PROJECT for a single project.

If you are not using GitHub-owned blob storage, see Configure blob storage.

Additional arguments

Reviewing the migration script

After you generate the script, review the file and, optionally, edit the script.

• If there are any repositories you don't want to migrate, delete or comment out the corresponding lines.
• If you want any repositories to have a different name in the destination organization, update the value for the corresponding --github-repo flag.
• If you want to change the visibility of a new repository, add or update the corresponding --target-repo-visibility flag.

Migrate repositories

If your trial run was successful, and you were able to complete the follow-up tasks, you can proceed to the real migration.

Run the script you generated. Replace FILENAME in the commands below with the filename you provided when generating the script.

• If you're using Terminal, use ./.

  Shell

  ./FILENAME
  

• If you're using PowerShell, use .\.

  Shell

  .\FILENAME