github-actions[bot]
commented
1 year ago 👋 Thank you for opening this migration issue.
The following 2 repositories have been parsed from your issue body:
https://github.com/casa-vega/ghec-to-ghes-migrations-via-actions-1
https://github.com/casa-vega/ghec-to-ghes-migrations-via-actions-2The target organization is set to be: ``
The target repository visibility is set to be: Internal
Troubleshooting
If the parsed repositories are not matching the repositories listed in your issue body, you can edit the issue body and make sure it's correct. List your repositories in a code block as this one: ``` https://source.example.com/your-org/your-repository-1 https://source.example.com/your-org/your-repository-2 ```Run the migration
Add a comment to this issue with one of the following two commands in order to run a migration:
Dry-run
We recommend to do a "dry-run" migration first which will not lock your source repository and therefore does not block your users from continuing to work on the repository.
/run-dry-run-migrationProduction
After you have verified your "dry-run" migration and after you have announced the production migration to your users, create a comment with the following command to start the production migration. It will lock your source repository and make it unaccessible for your users.
/run-production-migration
cvega
Repositories
Target repository visibility
Internal