GitHub provides a migrations API which allows us to archive out the entirety of metadata out of rust-lang/rust and associated repositories.
Although everyone with checkouts can restore the source, we currently have no meaningful backups of the issues, PRs, comments and other useful metadata.
Backup SaaS providers are prohibitively expensive - but the GitHub migrations API provides multiple ways to pull an archived version of all this metadata which we can then restore. We should look at some of the open-source solutions for this, and periodically back up the entirety of the rust-lang org to our gcp backup buckets from #122.
GH Migration API
python-github-backup
#t-infra > Hypothetical Github to Forgejo move @ 💬
GitHub provides a migrations API which allows us to archive out the entirety of metadata out of rust-lang/rust and associated repositories.
Although everyone with checkouts can restore the source, we currently have no meaningful backups of the issues, PRs, comments and other useful metadata.
Backup SaaS providers are prohibitively expensive - but the GitHub migrations API provides multiple ways to pull an archived version of all this metadata which we can then restore. We should look at some of the open-source solutions for this, and periodically back up the entirety of the rust-lang org to our gcp backup buckets from #122.
GH Migration API
python-github-backup
#t-infra > Hypothetical Github to Forgejo move @ 💬