3 ms·
Not being able to pull from or push to the git remote is pretty low on the list of problems when GitHub goes down. If that’s the main problem I’ll just set up g
by oefrha 7y ago
Not being able to pull from or push to the git remote is pretty low on the list of problems when GitHub goes down. If that’s the main problem I’ll just set up gitolite on a server (and I do) and call it a day.
All the issue/PR discussions and CI/CD are the real problems, and this doesn’t seem to help at all, so good luck collaborating without changing your workflow when GitHub is down.
- michaelmure 7y agoShameless plug regarding the issues: https://github.com/MichaelMure/git-bug https://github.com/MichaelMure/git-bug
- cap10morgan 7y agoCool! We'll look into that.
- cap10morgan 7y agoOur setup process is a much lighter lift than standing up a server and installing gitolite on it. But yes, if GitHub is down, then your workflow is going to change. We're hoping to close that gap down the road, but having a way to continue pushing and pulling with collaborators with a very quick setup seemed compelling to us. Not to mention the benefits that decentralization itself brings. The vast majority of git users tend to agree on one "origin" remote and 99-100% of their pushes and pulls are to/from that remote. So git, in practice, tends to be centralized when it comes time to collaborate with others. We're trying to re-decentralize that aspect while accommodating the convenient workflows we're all used to.
- oefrha 7y ago> Our setup process is a much lighter lift than standing up a server and installing gitolite on it. I think a counter to that is only one person needs to set up the additional git remote, compared to everyone having to install additional software to use dgit.
- cap10morgan 7y agoTotally fair. We definitely want to make that install process very simple and fast for as many people as we can. And it only needs to be done once per machine. :)