Skip to content

Latest commit

 

History

History
69 lines (49 loc) · 4.08 KB

migrating-to-internal-repositories.md

File metadata and controls

69 lines (49 loc) · 4.08 KB
Raw
title intro redirect_from permissions versions type topics shortTitle
Migrating to internal repositories
You can migrate to internal repositories to unify the innersource experience for developers using both {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}.
/enterprise/admin/installation/migrating-to-internal-repositories
/enterprise/admin/user-management/migrating-to-internal-repositories
/admin/user-management/migrating-to-internal-repositories
/admin/user-management/managing-repositories-in-your-enterprise//migrating-to-internal-repositories
Site administrators can migrate to internal repositories.
ghes
<3.10
how_to
Enterprise
Privacy
Repositories
Security
Internal repository migration

About internal repositories

Internal repositories are available in {% data variables.product.prodname_ghe_server %} 2.20+. {% data reusables.repositories.about-internal-repos %} For more information, see "AUTOTITLE."

In future releases of {% data variables.product.prodname_ghe_server %}, we will adjust how repository visibility works so that the terms public, internal, and private have a uniform meaning for developers on {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}.

To prepare for these changes, if you have private mode enabled, you can run a migration on your instance to convert public repositories to internal. This migration is currently optional, to allow you to test the changes on a non-production instance. The migration will become mandatory in the future.

When you run the migration, all public repositories owned by organizations on your instance will become internal repositories. If any of those repositories have forks, the forks will become private. Private repositories will remain private.

All public repositories owned by user accounts on your instance will become private repositories. If any of those repositories have forks, the forks will also become private. The owner of each fork will be given read permissions to the fork's parent.

Anonymous Git read access will be disabled for each public repository that becomes internal or private.

If your current default visibility for repositories is public, the default will become internal. If the current default is private, the default will not change. You can change the default at any time. For more information, see "AUTOTITLE."

The repository creation policy for the instance will change to disable public repositories and allow private and internal repositories. You can update the policy at any time. For more information, see "AUTOTITLE."

If you don't have private mode enabled, the migration script will have no effect.

Running the migration

  1. Connect to the administrative shell. For more information, see "AUTOTITLE." {% ifversion ghes %}

  2. Run the migration command.

    github-env bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log

{% else %}

  1. Navigate to the /data/github/current directory.

    cd /data/github/current

  2. Run the migration command.

    sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log

{% endif %}

Log output will appear in the terminal and /tmp/convert_public_ghes_repos_to_internal.log.

Further reading