Dylan Smith
Dylan Smith
re-opening this, as it does represent a bug in the CLI retry logic that we should still come back and fix.
are we sure that it's always safe to retry when we get SERVICE_UNAVAILABLE? What if the migration was halfway through, then got a SERVICE_UNAVAILABLE. Does the migration clean up after...
We could alleviate the retry/failure concern by only deleting the archive at the end of the migrate-repo command AFTER everything has succeeded. If the github ingest fails we don't delete....
Thanks for the suggestion! cc @timrogers for the feature request
> Or perhaps not... For some reason, none of the workflows in my fork appear in the Actions tab of my fork! > > Would love to dispatch the CI...
I no longer work on the gei eng team (I just lurk in the repo), so one of the engineers from that team will have to shepherd this PR in.
FYI the reason we haven't historically added support for additional architectures is because we don't have access to machines to test it easily. Adding the additional compile targets is relatively...
What’s the command you are running? Be sure you’re not passing ghes-api-url or it will always try to generate new archive.
can you share the exact combination of args you are using?
> something like > > ``` > gh gei migrate-repo --github-source-org XXXX --source-repo XXXX --github-target-org XXXX --target-repo XXXXX --ghes-api-url https://github-blah.com/api/v3 > ``` I thought you were using the archive-path args??