Is there any guides/best practices/manuals describing how to organize periodical backup (and of course restore if needed) of entire organization's GitHub, preferably with metadata?
2
github
-
hmmm I think you've missed the point of "distributed" version control. While you might have additional metadata in github (e.g. user accounts, ssh keys) all the data which has ever been checked in along with labels and will be replicated anywhere you do a git clone or git pull– symcbeanJul 10 at 17:13
-
Indeed, but the problem is that I need it with all metadata– Someone SometimeJul 10 at 19:26
Add a comment
|
1 Answer
https://docs.github.com/en/repositories/archiving-a-github-repository/backing-up-a-repository
Backing up a repository
You can use the API or a third-party tool to back up your repository.
To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "Migrations."
Once you have downloaded your archive, you can copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as Azure Blob Storage, Google Drive or Dropbox.
Migrations
https://docs.github.com/en/rest/migrations?apiVersion=2022-11-28
Third-party backup tools
A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive all public repositories on GitHub that have not opted out and make the data accessible to anyone, backup tools will download data from specific repositories and organize it within a new branch or directory. For more information about archival projects, see "About archiving content and data on GitHub." For more information about self-service backup tools, see the Backup Utilities category on GitHub Marketplace.
https://github.com/marketplace?category=backup-utilities
You can also have an on-premises endpoint synchronize with all of your repos. That endpoint is backed up.
