Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fail fast if the target GitHub repo already exists in bbs2gh migrate-repo #1087

Merged
merged 3 commits into from
Aug 2, 2023
Merged

Fail fast if the target GitHub repo already exists in bbs2gh migrate-repo #1087

merged 3 commits into from
Aug 2, 2023

Commits on Aug 2, 2023

  1. Fail fast if the target GitHub repo already exists in `bbs2gh migrate… 

    …-repo`

Looking at our error logs, it's clear that customers frequently
start Bitbucket migrations, waiting for the export to run, and
then discover that the  migration can't happen because the target
repo already exists.

This wastes a bunch of time, since Bitbucket archive generation
can be reasonably slow!

This changes the behaviour of `bbs2gh migrate-repo` to match
what `gei migrate-repo` does for GHES migrations: check if the
target repo already exists *before* running the export.

This should only happen when `migrate-repo` is run with a
combination of arguments that includes GitHub credentials - so
not the export-only or the export-and-download modes.

Fixes #1086.
    @timrogers
    timrogers committed Aug 2, 2023
    Configuration menu
    Copy the full SHA
    4946da2 View commit details
    Browse the repository at this point in the history

  2. Update release notes

    @timrogers
    timrogers committed Aug 2, 2023
    Configuration menu
    Copy the full SHA
    0300371 View commit details
    Browse the repository at this point in the history

  3. Fix red test

    @timrogers
    timrogers committed Aug 2, 2023
    Configuration menu
    Copy the full SHA
    066c34e View commit details
    Browse the repository at this point in the history