GitHub Down Again?

Every time there's an outage with $SCMProvider, there's always a comment like this.

Git is not GitHub. GitHub is not git.

You can absolutely do git in a distributed way.

That doesn't help when your business workflow relies on GitHub for access control, artifact hosting, issue management, PR coordination & approval, and all the thousand other things that people use GitHub for.

I mean... it still is? I can work on my codebase and commit on my local machine. Push remote to Gitlab if Github is down. When Github is back up I can push to Github. What's the problem?

To answer most comments here, of course git is still decentralized, it’s just that almost no one use it like that. We chose the easier route, as usual. Just like most people don’t host their texts and photos on their own site.

I simply expected more from us nerds.

It still is one, but it’s easier to work with it if there’s a single source of truth.

You can still work on your Git tree, you just can’t sync with this SSOT.

Note that your repo stays usable even while GitHub is down, and your team can sync their work afterwards. Or if you prefer, you can switch to a different remote without much trouble.

On a different note, I do host my own Git server, but between maintainance downtime, power outages and ISP issues, my availability isn't nearly as good as GitHub's.

This joke is more beaten than Github at this point.

Git is decrentralized! You win GitHub down bingo!

"operational" comes with strings attached. We don't know what internal SLAs specify but most likely the service is meeting those agreements.

Should we get a refund? :)

"When a metric becomes a target, it ceases to be a good metric"

I regret that uptime became a clause in SLAs, or a reputation/marketing thing. I don't care about how many 9s are after your decimal, I just want to know if your service is down or if something is wrong on my end.

One of the many status page/"is it down" services could probably get some good PR out of having a GitHub status page that's based upon live results from several geographical locations..

They have reported incidents for the last two days but seem to limit it to a short amount of time which is clearly not the case for many folks out there.

I know over on AWS they are loath to update the status page since this is tied to SLA compensation. Does github have the same problem?

Once Tableau was acquired by Salesforce, shit that had been stable as can be for YEARS started to break as Tableau (I assume) began to interface with SF systems or requirements. Last week, CLI functionality was down for 3-4 days, depending on the cluster you're on. Nothing like crushing production reporting for a week at the end of the month because Salesforce wants X, Y, and Z added to a mature product that had seen no issues for the 3 years prior.

My guess is that is the same sort of thing happening here w/Microsoft.

Might simply be infrastructure consolidation since Microsoft bought them. Same reason behind the Azure pipe / GitHub Actions mess.

Probably just Windows Update /s

> Repost: https://news.ycombinator.com/item?id=32735734

LOL, this clearly shows how grave the situation is. Guess it's time to listen again to: https://youtu.be/XimyEvDJWzA

That post is a day old

One of many.

same here