Skip to main content

Follow-up tasks

After each migration has finished, you'll need to complete some additional tasks before the repository is ready for work.

Checking the migration status

First, check whether your migration succeeded or failed.

The way you check the status of your migration depends on how you ran the migration.

  • If you ran the migration using the GitHub CLI, by default, the process will display whether the migration succeeded or failed once the migration is complete. If the migration failed, you will see the reason for failure.

    Migration completed (ID: RM_123)! State: SUCCEEDED
    
  • If you ran the migration using the GitHub CLI with the optional --queue-only argument, the process will exit immediately after queueing the migration, and will not tell you if the migration succeeded or failed. You can check a migration's status using the wait-for-migration command, or by reviewing the migration log.

Reviewing the migration log

You should review the migration log for each migrated repository. People with read access to a repository can access the migration log for the repository on GitHub.

  1. Navigate to the migrated repository in your destination organization.

  2. 在仓库名称下,单击 “Issues”****。

    存储库的主页的屏幕截图。 在水平导航栏中,标记有“问题”的选项卡以深橙色标出。

  3. Click the issue with the title "Migration Log."

For more information, see 访问 GitHub Enterprise Importer 的迁移日志.

Setting repository visibility

默认情况下,所有存储库都作为专用存储库迁移,只有运行迁移的用户和组织所有者才有权访问存储库。 如果不希望存储库是私有的,请更改可见性。

  • 可以在浏览器中更改存储库的可见性。 有关详细信息,请参阅“设置存储库可见性”。

  • 或者,可以使用 GitHub CLI 命令行更改存储库可见性。 有关详细信息,请参阅gh repo editGitHub CLI文档中的信息。

    For example, replace YOUR_ORG with your organization name, and the command below will set all of the organization's repositories to internal visibility.

    Bash
    export ORG=YOUR_ORG
    gh repo list "$ORG" --limit 100000 --json name -q '.[].name' | xargs -I{} gh repo edit "$ORG/{}" --visibility internal
    

Reclaiming mannequins

运行迁移GitHub Enterprise ImporterEnterprise Live Migrations后,迁移存储库(Git 提交除外)中的所有用户活动都归因于称为 mannequins 的占位符标识。

注意

只有组织所有者才能回收模型。 如果已获得迁移者角色,请联系组织所有者执行此步骤。

  1. 决定是否要回收模型。
  2. 计划何时完成回收。
  3. 回收人体模型。 可以使用 GitHub CLI 或浏览器中将每个人模的历史记录重新分配给组织成员。 如果你使用 GitHub CLI,可以批量回收占位资源。 有关详细信息,请参阅“回收 GitHub Enterprise Importer 的模型”。
  4. 如果任何成员尚未通过团队成员身份具有存储库的适当访问权限,请授予该成员对存储库的访问权限。 有关详细信息,请参阅“管理个人对组织仓库的访问”。

Configuring IP allow lists

If you added the IP ranges for GitHub Enterprise Importer to the IP allow list for your destination organization, you can remove those entries. 如果为目标企业禁用了标识提供者的 IP 允许列表限制,现在可以重新启用它们。