If only there was some kind of distributed version control system. /s

thanksforfish · on April 2, 2020

Of course, there is. You just need to host it. Self-hosted GitLab mirrors work great when GitHub is down.

https://docs.gitlab.com/ee/user/project/repository/repositor...

Seirdy · on April 2, 2020

Instead of relying on GitLab's API, it's probably a better idea to just use git remotes properly. I put together a script [0] to automate the process to set the primary remote to Sourcehut (git.sr.ht) and mirror to GitLab and GitHub. And yes, that script is in a repo that's also mirrored to GitHub and GitLab (check the README). It combines well with my `git pushall` alias [1].

[0]: https://git.sr.ht/~seirdy/dotfiles/tree/master/Executables/s...

[1]: https://git.sr.ht/~seirdy/dotfiles/tree/master/.config/git/c...

jakejarvis · on April 2, 2020

Or Gitea, if you want to use a fraction of the resources! I use it solely as a GitHub backup — you can mirror Git repositories from anywhere and it pulls changes on a schedule. Literally set it up this week, thank goodness.

https://gitea.io/en-us/

juancampa · on April 2, 2020

I think he meant git itself

gumby · on April 2, 2020

You can just sync with someone else’s repo by specifying it on the command line. Nothing to install, no script, nothing. It’s built into git and is right there in the single line summary of the man pages for git-fetch, git-pull etc: they all take a repository argument.

mr_toad · on April 2, 2020

Managing keys for all the contributors quickly gets to be a chore.

Identity management is what Github really is all about.