GitHub Reliability Concerns
Discussions focus on GitHub's frequent outages, risks of centralization, and the ease of switching to alternatives due to Git's decentralized nature, with recommendations for self-hosting like GitLab or Gitea.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Github is only a high profile Git peer. If it explodes someone just pushes up to a different repo hosting site or goes back to trading chagesets some other way.
How is it at all odd? Github offers a convenient platform for using git. People use it.If Github were to explode forever tomorrow, active projects would just take their locally cloned repositories, and put them online somewhere else and carry on committing (albeit sans github's awesome social tools). That's the real power git offers us.It's just a fact of reality that most projects centrally organize through a few bottlenecks. It's easier for people to remember where to go, if t
Looks like relying on a centralised github isn't the most reliable choice. It's convenient, but if you don't want to be held ransom by Microsoft's decisions, then a self hosted repository has to be the way forwards.
You don't have to compromise, you just have to evaluate. What could go wrong ? In this case, the worst thing that can happen is that you have to get your data and move, which are both easy to do.So what you can do is:- create a git lab instance as a synchronized unused backup that doesn't require a lot of maintenance to work.- use github as the main dev plateform.- then if (and it's a biiiiiig if) something ever go wrong, you switchThe benefits are huge :- much l
If github goes down/becomes evil wouldn't it be trivial to just push your repo to another host? I guess there's other things that might tie you into their ecosystem, like wiki/issue tracking/static hosting, but git itself makes it pretty easy to just push elsewhere...
Yes. Once again. [0]Due to GitHub's chronic unreliability, it is guaranteed to continue happening every month.Looks like avoiding to 'centralize everything to GitHub' has aged very well [1] and at this point you would get better uptime with self-hosting instead of using GitHub.Just ask many open source organizations like RedoxOS, ReactOS, wireguard, GNOME, KDE, etc.[0] https:/&#x
I don't see how GitHub is a single point of failure, the tool was developed on an internal Gitlab instance and then just pushed to GitHub. In case anything happens to GitHub you'd just have to push it to some new service and update the website. Nothing will be lost.It's just more exposure to put it on GitHub right now because most people bookmark/star there repositories there and don't want to bookmark different cgit/Gitlab/gogs/gitea links. I don'
One of the benefits of gitlab is you can host it yourself. Github has also had outages.
Is there still no safe alternative to GitHub?
If github opensource all of their stuff, this still wouldn't prevent issues like this for the projects that want to use a hosted service instead of hosting it themselves, and many projects don't want to host these services them selves anymore.When I worry about dependency on GitHub, I'm thinking about not the inconvenient hours of downtime but the larger threat that they might disappear or turn evil.What I would like to see even more than opensource github would be a standar