Use the `--wait` option in all GEI `migrate-repo` examples (#35998)

Co-authored-by: Laura Coursen <lecoursen@github.com>
This commit is contained in:
Tim Rogers 2023-03-30 15:03:05 +01:00 коммит произвёл GitHub
Родитель 4e40d620b5
Коммит 30141addd5
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
5 изменённых файлов: 16 добавлений и 5 удалений

Просмотреть файл

@ -223,9 +223,11 @@ You can migrate multiple repositories with a migration script or a single reposi
To migrate a single repository, use the `gh ado2gh migrate-repo` command.
```shell{:copy}
gh ado2gh migrate-repo --ado-org SOURCE --ado-team-project TEAM-PROJECT --ado-repo CURRENT-NAME --github-org DESTINATION --github-repo NEW-NAME
gh ado2gh migrate-repo --ado-org SOURCE --ado-team-project TEAM-PROJECT --ado-repo CURRENT-NAME --github-org DESTINATION --github-repo NEW-NAME --wait
```
{% data reusables.enterprise-migration-tool.wait-flag %}
{% data reusables.enterprise-migration-tool.migrate-repo-table-ec %}
## Step 6: Validate your migration and check the error log

Просмотреть файл

@ -176,6 +176,7 @@ To migrate a single repository, use the `gh bbs2gh migrate-repo` command.
gh bbs2gh migrate-repo --bbs-server-url BBS-SERVER-URL \
--bbs-project PROJECT --bbs-repo CURRENT-NAME \
--github-org DESTINATION --github-repo NEW-NAME \
--wait \
# Use the following options if your Bitbucket Server instance runs on Linux
--ssh-user SSH-USER --ssh-private-key PATH-TO-KEY
# Use the following options if your Bitbucket Server instance runs on Windows
@ -184,6 +185,8 @@ gh bbs2gh migrate-repo --bbs-server-url BBS-SERVER-URL \
--aws-bucket-name AWS-BUCKET-NAME
```
{% data reusables.enterprise-migration-tool.wait-flag %}
{% data reusables.enterprise-migration-tool.placeholder-table %}
{% data reusables.enterprise-migration-tool.bbs-server-url-placeholder %}
{% data reusables.enterprise-migration-tool.project-placeholder %}

Просмотреть файл

@ -454,23 +454,25 @@ If you're migrating from {% data variables.product.prodname_ghe_server %} 3.7 or
If you're using {% data variables.product.prodname_ghe_server %} 3.8 or later, use the following flags:
```shell{:copy}
gh gei migrate-repo --github-source-org SOURCE --source-repo CURRENT-NAME --github-target-org DESTINATION --target-repo NEW-NAME --ghes-api-url GHES-API-URL
gh gei migrate-repo --github-source-org SOURCE --source-repo CURRENT-NAME --github-target-org DESTINATION --target-repo NEW-NAME --ghes-api-url GHES-API-URL --wait
```
If you're migrating from {% data variables.product.prodname_ghe_server %} 3.7 or earlier and using Azure Blob Storage as your blob storage provider, use the following flags to authenticate:
```shell{:copy}
gh gei migrate-repo --github-source-org SOURCE --source-repo CURRENT-NAME --github-target-org DESTINATION --target-repo NEW-NAME \
--ghes-api-url GHES-API-URL --azure-storage-connection-string "AZURE_STORAGE_CONNECTION_STRING"
--ghes-api-url GHES-API-URL --azure-storage-connection-string "AZURE_STORAGE_CONNECTION_STRING" --wait
```
If you're migrating from {% data variables.product.prodname_ghe_server %} 3.7 or earlier and using Amazon S3 as your blob storage provider, use the following flags to authenticate:
```shell{:copy}
gh gei migrate-repo --github-source-org SOURCE --source-repo CURRENT-NAME --github-target-org DESTINATION --target-repo NEW-NAME \
--ghes-api-url GHES-API-URL --aws-bucket-name "AWS-BUCKET-NAME"
--ghes-api-url GHES-API-URL --aws-bucket-name "AWS-BUCKET-NAME" --wait
```
{% data reusables.enterprise-migration-tool.wait-flag %}
{% data reusables.enterprise-migration-tool.ssl-flag %}
{% data reusables.enterprise-migration-tool.skip-releases %}

Просмотреть файл

@ -196,8 +196,11 @@ gh gei generate-script --github-source-org SOURCE --github-target-org DESTINATIO
{% data reusables.enterprise-migration-tool.gei-migrate-repo %}
```shell{:copy}
gh gei migrate-repo --github-source-org SOURCE --source-repo CURRENT-NAME --github-target-org DESTINATION --target-repo NEW-NAME
gh gei migrate-repo --github-source-org SOURCE --source-repo CURRENT-NAME --github-target-org DESTINATION --target-repo NEW-NAME --wait
```
{% data reusables.enterprise-migration-tool.wait-flag %}
{% data reusables.enterprise-migration-tool.skip-releases %}
{% data reusables.enterprise-migration-tool.migrate-repo-table-ec %}

Просмотреть файл

@ -0,0 +1 @@
The command will keep running until your migration finishes.