Remove GHAE in Liquid and front matter (22) (#49015)
This commit is contained in:
Peter Bengtsson
@@ -6,7 +6,6 @@ versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
ghae: '*'
|
||||
---
|
||||
|
||||
## About migration paths to GitHub
|
||||
@@ -43,7 +42,7 @@ You can review the scope and tooling for your migration to {% data variables.pro
|
||||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**:
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
|
||||
- **Caveats**:
|
||||
- {% data reusables.migrations.large-repositories-require-expert-services %}
|
||||
@@ -54,7 +53,7 @@ You can review the scope and tooling for your migration to {% data variables.pro
|
||||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**:
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
|
||||
- **Caveats**:
|
||||
- {% data reusables.migrations.large-repositories-require-expert-services %}
|
||||
@@ -67,7 +66,7 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
|
||||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %} or {% data variables.product.prodname_expert_services %}
|
||||
- **More information**:
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
|
||||
- **Caveats**:
|
||||
- {% data reusables.migrations.large-repositories-require-expert-services %}
|
||||
@@ -77,7 +76,7 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
|
||||
|
||||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**: "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- **More information**: "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
|
||||
### Azure DevOps Server to {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
||||
@@ -85,7 +84,7 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
|
||||
- **Tooling**: Migration to Azure DevOps Services, then {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**:
|
||||
- [Migrate data from Azure DevOps Server to Azure DevOps Services](https://learn.microsoft.com/en-us/azure/devops/migrate/migration-overview?view=azure-devops) in the Microsoft Docs
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- **Caveats**: If you can't migrate to Azure DevOps Services first, you must perform a "source and history" migration instead. For more information, "[Migrations from any Git repository to {% data variables.product.prodname_dotcom_the_website %}](#migrations-from-any-git-repository)."
|
||||
|
||||
### Bitbucket Cloud (Bitbucket.org) to {% data variables.product.prodname_dotcom_the_website %}
|
||||
@@ -101,7 +100,7 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
|
||||
- **Scope**: Source, history, and metadata
|
||||
- **Tooling**: {% data variables.product.prodname_importer_proper_name %}
|
||||
- **More information**:
|
||||
- "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer)"
|
||||
- "[AUTOTITLE](/migrations/using-github-enterprise-importer)"
|
||||
- [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
|
||||
- **Caveats**:
|
||||
- For complex repositories larger than around 5 GB, you may need to use `bbs-exporter` and Enterprise Cloud Importer instead. Enterprise Cloud Importer is only available for expert-led migrations.
|
||||
|
||||
@@ -6,7 +6,6 @@ versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
ghae: '*'
|
||||
---
|
||||
|
||||
## About migrations
|
||||
@@ -60,9 +59,9 @@ If you’re migrating from {% data variables.product.prodname_ghe_cloud %} or {%
|
||||
|
||||
{% data reusables.enterprise-migration-tool.gh-repo-stats-not-supported %}
|
||||
|
||||
If you’re migrating from Azure DevOps, we recommend the `inventory-report` command in the {% data variables.product.prodname_ado2gh_cli %}. The `inventory-report` command will connect with the Azure DevOps API, then build a simple CSV with some of the fields suggested above. For more information about how to install the {% data variables.product.prodname_ado2gh_cli %}, see "[AUTOTITLE]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/migrating-repositories-from-azure-devops-to-github-enterprise-cloud)."
|
||||
If you’re migrating from Azure DevOps, we recommend the `inventory-report` command in the {% data variables.product.prodname_ado2gh_cli %}. The `inventory-report` command will connect with the Azure DevOps API, then build a simple CSV with some of the fields suggested above. For more information about how to install the {% data variables.product.prodname_ado2gh_cli %}, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/migrating-repositories-from-azure-devops-to-github-enterprise-cloud)."
|
||||
|
||||
If you’re migrating from Bitbucket Server or Bitbucket Data Center, we recommend the `inventory-report` command in the {% data variables.product.prodname_bbs2gh_cli %}. The `inventory-report` command will use your Bitbucket instance's API to build a simple CSV. For more information about how to install the {% data variables.product.prodname_bbs2gh_cli %}, see "[AUTOTITLE]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud)."
|
||||
If you’re migrating from Bitbucket Server or Bitbucket Data Center, we recommend the `inventory-report` command in the {% data variables.product.prodname_bbs2gh_cli %}. The `inventory-report` command will use your Bitbucket instance's API to build a simple CSV. For more information about how to install the {% data variables.product.prodname_bbs2gh_cli %}, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud)."
|
||||
|
||||
For other migration origins, create your migration inventory yourself. You could build the spreadsheet using the origin’s reporting tools, if available, or API, or you could create the inventory manually.
|
||||
|
||||
@@ -202,7 +201,7 @@ For example, suppose @octocat created an issue on {% data variables.location.pro
|
||||
The way that attribution works differs between tools:
|
||||
|
||||
- If you’re using `ghe-migrator`, `gl-exporter`, or `bbs-exporter`, you will decide how you want to attribute data ahead of time and include a mapping file when you import your data.
|
||||
- If you’re using {% data variables.product.prodname_importer_proper_name %}, data will be linked to placeholder identities called “mannequins”, and you can assign this history to real users after your data is migrated. For more information, see "[AUTOTITLE]({% ifversion ghae %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer)."
|
||||
- If you’re using {% data variables.product.prodname_importer_proper_name %}, data will be linked to placeholder identities called “mannequins”, and you can assign this history to real users after your data is migrated. For more information, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer)."
|
||||
|
||||
### Managing teams and permissions
|
||||
|
||||
|
||||
Reference in New Issue
Block a user