You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the migrate-repo command is run for bbs2gh and bbs2gh there is an output at the end of both a successful and unsuccessful command.
Should we be returning both the hyperlink and the command to download the migration log in this output:
Currently:
Migration log available at https://objects-origin.githubusercontent.com/octoshiftmigrationlogs/import-testing/unicorn-8be6809e-060d-4470-aa38-83741db95a92-logs.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=octoshiftstoragedev%2F20231019%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20231019T151543Z&X-Amz-Expires=432000&X-Amz-Signature=52365bf878754944d80ba7b07887c26e365601a66cec306d6b1c2057bb936f07&X-Amz-SignedHeaders=host or by running `gh ado2gh download-logs --github-org import-testing --github-repo unicorn`
The text was updated successfully, but these errors were encountered:
This is by design and deliberate, something that was done in #706 to further encourage customers to open the migration log. Basically another way of viewing the migration log.
Description
When the migrate-repo command is run for
bbs2gh
andbbs2gh
there is an output at the end of both a successful and unsuccessful command.Should we be returning both the hyperlink and the command to download the migration log in this output:
Currently:
The text was updated successfully, but these errors were encountered: