zlacker

Again? Last time this happened was 5 days ago. [0]

It is not even the end of the month and the outages are increasing every month and it is now chronically unreliable. Seriously, we have given GitHub more than 3 years to improve and it clearly isn't working. That is plenty of time.

At this point, you might as well self-host like the rest of the open source projects out there, since GitHub is falling apart every week and it seems to be more reliable to self-host than to sit on GitHub, go all in and tolerate these outages every calendar month.

[0] https://news.ycombinator.com/item?id=35903116

>>rvz+(OP)
I mean one of the beauty parts of git has always been that you can and, under ideal best practices, should have more than one place to put your code with the distributed nature of it

>>jamal-+s
I dunno about "should", that feels like overkill. Expecting to get something like a 99.99% SLA shouldn't be unreasonable to expect out of a hosted solution

>>jamal-+s
The value add for Github is mostly the issue/PR interface and actions.

>>rvz+(OP)
Yeah, they had incidents the 9th, the 10th, and the 11th. So this is the fourth incident this month.

>>willsm+91
A seperate git remote isn't incredibly unreasonable either - Even if it's just something on localhost in case of scenarios like this one

Github being down for a bit shouldn't disrupt your work flow

>>jamal-+G2
GitHub being down blocks all of our CI pipelines, for example.

>>jamal-+s
But also, and more relevantly here, git is designed to be usable entirely offline. And if you do need to have some connection with remotes, git allows you to do so extremely sporadically if your network connectivity, or remote availability, is limited.

>>maccar+W2
you should be able to run the basic tests locally.

>>jamal-+s
But currently that's not the beauty part of GitHub, it's the actions, discoverability and other features not part of Git.