Set multiple urls for one remote using `--push`
https://git-scm.com/docs/git-remote#git-remote-emset-urlem
and you are about done.
This is only a partial solution, right?
Services such as Backhub.co also backup your issues:
https://backhub.co/features/backup-github-issues/
(we have 1000+ closed issues in our project, nice to preserve)
Right. The service is certainly expected to do more. Was mostly addressing the issue of mirroring the data to dropbox. But even then my "solution" only saves whatever you do locally. So if you merge PRs through github, it wouldn't get mirrored.
If you have self-deployed Gogs (which is a smallish OSS GitHub clone) you can easily set it to mirror other repositories periodically. Very useful for backups.
Also simple to self-deploy since it's essentially a single service written in Go.
Check out Gitea, which is a community managed fork of Gogs.
If you're writing research software you can backup to zenodo (i.e. CERN) for free.
Re:A fork on GitHub is no fork
by knownothing on Friday March 16, 2018 @12:13PM
(#16601599)
>Has anyone created a service that you auth in through GitHub and it backs up all your repos to S3 or Dropbox or something? I'd pay a few bucks for something like that.
So you'd pay money for a tool that copies your data, but not simply pay the money to access said data?
This doesn't make any sense at all.
Edit: I found backhub.co. Unfortunately their pricing is per-repo and my usage model involves lots of tiny repos.