forked from github/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request github#30778 from github/repo-sync
Repo sync
- Loading branch information
Showing
16 changed files
with
257 additions
and
200 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
125 changes: 125 additions & 0 deletions
125
...r/migrating-between-github-products/about-migrations-between-github-products.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,125 @@ | ||
| --- | ||
| title: About migrations between GitHub products | ||
| shortTitle: About migrations | ||
| intro: 'Learn which data {% data variables.product.prodname_importer_proper_name %} can migrate between {% data variables.product.company_short %} products.' | ||
| versions: | ||
| fpt: '*' | ||
| ghes: '*' | ||
| ghec: '*' | ||
| --- | ||
|
|
||
| ## About migrations between GitHub products | ||
|
|
||
| With {% data variables.product.prodname_importer_proper_name %}, you can migrate data from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}, or migrate data between accounts on {% data variables.product.prodname_ghe_cloud %}. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer)." | ||
|
|
||
| If your migration source is another account on {% data variables.product.prodname_dotcom_the_website %}, you can migrate individual repositories between organizations, or migrate entire organizations between enterprises. If your migration source is {% data variables.product.prodname_ghe_server %}, you can migrate repositories. | ||
|
|
||
| The data that {% data variables.product.prodname_importer_proper_name %} migrates depends on the source of the migration and whether you are migrating a repository or organization. | ||
|
|
||
| ## Data that is migrated from {% data variables.product.prodname_ghe_server %} | ||
|
|
||
| To migrate from {% data variables.product.prodname_ghe_server %} (GHES), you must have GHES version 3.4.1 or higher. The data that is migrated depends on the version you're using. | ||
|
|
||
| Item | GHES 3.4.1+ | GHES 3.5.0+ | | ||
| ---- | ---------- | ---------- | | ||
| Git source (including commit history) | **X** | **X** | | ||
| Pull requests | **X** | **X** | | ||
| Issues | **X** | **X** | | ||
| Milestones | **X** | **X** | | ||
| Wikis | **X** | **X** | | ||
| Projects (classic) at the repository level | **X** | **X** | | ||
| {% data variables.product.prodname_actions %} workflows | **X** | **X** | | ||
| Commit comments | **X** | **X** | | ||
| Active webhooks | **X** | **X** | | ||
| Branch protections | **X** | **X** | | ||
| {% data variables.product.prodname_pages %} settings | **X** | **X** | | ||
| User history for the above data | **X** | **X** | | ||
| Releases | | **X** | | ||
|
|
||
| Different size limits per repository apply depending on your GHES version. | ||
|
|
||
| Limit | GHES <3.8.0 | GHES 3.8.0+ | | ||
| ----- | ----------- | ----------- | | ||
| Git source | 2GB | 10GB | ||
| Metadata | 2GB | 10GB | ||
|
|
||
| {% data reusables.enterprise-migration-tool.data-not-migrated %} | ||
| - Teams | ||
| - User or team access to the repository | ||
| - Repository settings for pull requests | ||
|
|
||
| ### Branch protections | ||
|
|
||
| {% data reusables.enterprise-migration-tool.branch-protection-migration %} | ||
|
|
||
| ## Data that is migrated from other accounts on {% data variables.product.prodname_dotcom_the_website %} | ||
|
|
||
| If your migration source is another account on {% data variables.product.prodname_dotcom_the_website %}, you can migrate individual repositories between organizations, or migrate entire organizations between enterprises. | ||
|
|
||
| ### Migrated data for an organization | ||
|
|
||
| When you migrate an organization, a new organization is created within the destination enterprise account. Then, the following data is migrated to the new organization. | ||
|
|
||
| - Teams | ||
| - Repositories | ||
| - Team access to repositories | ||
| - Member privileges | ||
| - Organization-level webhooks (must be re-enabled after your migration, see "[Enabling webhooks](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#enabling-webhooks)") | ||
| - Default branch name for new repositories created in the organization | ||
|
|
||
| All repositories are migrated with private visibility. If you want to set a repository's visibility to public or internal, you can do this after the migration using the UI or API. | ||
|
|
||
| Team membership is **not** migrated. After the migration, you'll need to add members to migrated teams. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#recreating-teams)." | ||
|
|
||
| {% note %} | ||
|
|
||
| **Note:** {% data reusables.enterprise-migration-tool.team-references %} For more information about how to prevent and resolve these issues, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer#team-references-are-broken-after-an-organization-migration)." | ||
|
|
||
| {% endnote %} | ||
|
|
||
| ### Migrated data for a repository | ||
|
|
||
| When you migrate a repository, either directly or as part of an organization migration, only the following data is migrated. | ||
|
|
||
| - Git source (including commit history) | ||
| - Pull requests | ||
| - Issues | ||
| - Milestones | ||
| - Wikis (excluding attachments) | ||
| - Projects (classic) at the repository level | ||
| - {% data variables.product.prodname_actions %} workflows | ||
| - Commit comments | ||
| - Active webhooks (must be re-enabled after your migration, see "[Enabling webhooks](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#enabling-webhooks)") | ||
| - Repository topics | ||
| - Repository settings | ||
| - Branch protections (see "[Branch protections](#branch-protections)" for more details) | ||
| - {% data variables.product.prodname_pages %} settings | ||
| - Autolink references | ||
| - {% data variables.product.prodname_GH_advanced_security %} settings | ||
| - Pull request settings | ||
| - Automatically delete head branches | ||
| - Allow auto-merge | ||
| - Allow merge commits (commit message setting is reset to the default message) | ||
| - Allow squash merging (commit message setting is reset to the default message) | ||
| - Allow rebase merging | ||
| - Releases (up to 10 GB per repository) | ||
| - User history for the above data | ||
|
|
||
| {% data reusables.enterprise-migration-tool.data-not-migrated %} | ||
| - User access to the repository | ||
|
|
||
| When you migrate a repository directly, teams and team access to repositories are not migrated. | ||
|
|
||
| #### Branch protections | ||
|
|
||
| {% data reusables.enterprise-migration-tool.branch-protection-migration %} | ||
|
|
||
| ## Limitations on migrated data | ||
|
|
||
| {% data reusables.enterprise-migration-tool.limitations-of-migrated-data %} | ||
|
|
||
| ## Getting started | ||
|
|
||
| Before you migrate between {% data variables.product.company_short %} products, you should plan out how you will run your migration. Before migrating any data, you will need to choose someone to run the migration. You must grant that person the necessary access for both the source and the destination of the migration. We also recommend you run a trial migration first. | ||
|
|
||
| For an overview of the migration process from beginning to end, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products)." |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
38 changes: 38 additions & 0 deletions
38
...terprise-cloud/about-migrations-from-azure-devops-to-github-enterprise-cloud.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| --- | ||
| title: About migrations from Azure DevOps to GitHub Enterprise Cloud | ||
| shortTitle: About migrations | ||
| intro: 'Learn which data {% data variables.product.prodname_importer_proper_name %} can migrate.' | ||
| versions: | ||
| fpt: '*' | ||
| ghes: '*' | ||
| ghec: '*' | ||
| --- | ||
|
|
||
| ## About migrations from Azure DevOps | ||
|
|
||
| You can use {% data variables.product.prodname_importer_proper_name %} to migrate repositories from Azure DevOps to {% data variables.product.prodname_ghe_cloud %}. | ||
|
|
||
| You can only use {% data variables.product.prodname_importer_proper_name %} to migrate from Azure DevOps Cloud, not from Azure DevOps Server. If you currently use Azure DevOps Server and want to migrate to {% data variables.product.prodname_dotcom %}, you can migrate to Azure DevOps Cloud first. For more information, see [Migrate to Azure DevOps](https://azure.microsoft.com/en-us/services/devops/migrate/) on the Azure site. | ||
|
|
||
| ## Data that is migrated | ||
|
|
||
| We currently only support migrating the following repository data from Azure DevOps to {% data variables.product.prodname_ghe_cloud %}. | ||
|
|
||
| - Git source (including commit history) | ||
| - Pull requests | ||
| - User history for pull requests | ||
| - Work item links on pull requests | ||
| - Attachments on pull requests | ||
| - Branch protections for the repository (user-scoped branch protections not included) | ||
|
|
||
| If you want to migrate Azure Pipelines to {% data variables.product.prodname_actions %}, contact your {% data variables.product.prodname_dotcom %} account manager. | ||
|
|
||
| ## Limitations on migrated data | ||
|
|
||
| {% data reusables.enterprise-migration-tool.limitations-of-migrated-data %} | ||
|
|
||
| ## Getting started | ||
|
|
||
| Before you migrate from Azure DevOps, you should plan out how you will run your migration. Before migrating any data, you will need to choose someone to run the migration. You must grant that person the necessary access for both the source and the destination of the migration. We also recommend you run a trial migration first. | ||
|
|
||
| For an overview of the migration process from beginning to end, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/overview-of-a-migration-from-azure-devops-to-github-enterprise-cloud)." |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40 changes: 40 additions & 0 deletions
40
...rise-cloud/about-migrations-from-bitbucket-server-to-github-enterprise-cloud.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| --- | ||
| title: About migrations from Bitbucket Server to GitHub Enterprise Cloud | ||
| shortTitle: About migrations | ||
| intro: 'Learn which data {% data variables.product.prodname_importer_proper_name %} can migrate.' | ||
| versions: | ||
| fpt: '*' | ||
| ghes: '*' | ||
| ghec: '*' | ||
| --- | ||
|
|
||
| ## About migrations from Bitbucket Server | ||
|
|
||
| You can use {% data variables.product.prodname_importer_proper_name %} to migrate repositories from Bitbucket Server to {% data variables.product.prodname_ghe_cloud %}. Migrations from Bitbucket Server are only supported for Bitbucket Server or Bitbucket Data Center version 5.14+ or higher. | ||
|
|
||
| ## Data that is migrated | ||
|
|
||
| We currently only support migrating the following repository data from Bitbucket Server to {% data variables.product.prodname_ghe_cloud %}. | ||
|
|
||
| - Git source (including commit history) | ||
| - Pull requests (including comments, pull request reviews, pull request review comments at the file and line level, required reviewers, and attachments) | ||
|
|
||
| ## Data that is not migrated | ||
|
|
||
| Currently, the following data is **not** migrated. | ||
|
|
||
| - Personal repositories owned by users | ||
| - Branch permissions | ||
| - Commit comments | ||
| - Repository settings | ||
| - CI pipelines | ||
|
|
||
| ## Limitations on migrated data | ||
|
|
||
| {% data reusables.enterprise-migration-tool.limitations-of-migrated-data %} | ||
|
|
||
| ## Getting started | ||
|
|
||
| Before you migrate from Bitbucket Server, you should plan out how you will run your migration. Before migrating any data, you will need to choose someone to run the migration. You must grant that person the necessary access for both the source and the destination of the migration. We also recommend you run a trial migration first. | ||
|
|
||
| For an overview of the migration process from beginning to end, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/overview-of-a-migration-from-bitbucket-server-to-github-enterprise-cloud)." |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.