69 comments

[ 2.0 ms ] story [ 176 ms ] thread
Hitting 500s when trying to push branches and create PRs.
Every day more Microsofty...they should rename to "Your Repository Needs To Restart To Apply Updates"
GitHub goes down at least once a week as I said before. [0] thanks to Copilot, Tay.ai and Zoe chatbots wrecking the platform instead of humans maintaining it.

If there was a prediction market for when GitHub experiences an outage every week, then you would make a lot of money.

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

And this is why I self host a lot of my Git stack with Gerrit...
I'm going to blame Claude Code!
At least it happened after I did my work for the day... jfc!
I've been sitting here waiting for a critical deploy to happen via GitHub Actions (I know, hour fault, we should have left ages ago). My patience for this bullshit is gone, I'm going to be pushing very hard to get us off of GitHub entirely except for public code mirrors going forward.

Edit: oh look, their site says all good, but I still have jobs stuck. What a pile of garbage.

I'm so sick of this.

Down? No sir we are not down. There are elevated error rates and degraded performance.
They invented the perfect solution to stop supply chain attacks.
Fuck sake. Again?

Sorry, I realise this comment isn't up to HN's usual standards for thoughtfulness and it is perhaps a bit inflammatory but... look, I'd bet the majority of us on this site rely on GitHub and I can't be the only one becoming incredibly frustrated with its recent unreliability[0]?

(And, yes, I did enough basic data analysis to confirm that it IS indeed getting worse versus a year, two years, and three years ago, and is particularly bad since the start of this year.)

[0] EDIT: clearly not from looking at the rest of the comments in this discussion.

Microslop at it again
I'm glad I moved over to forgejo. Being selfhosted, the UI loads faster. Most importantly, the thing is always responsive.
Took a full 8 years for a Microsoft acquisition to go to shit, which is probably a record. Kudos to the Github team for holding out this long.
The worst part of all this is that GitHub's CTO and VP of Engineering sent out the usual "here's what we'll do to fix things" letter to their larger customers and, without exaggeration, it boiled down to: 1) "Here's a bunch of stuff we already did!" which... clearly isn't working, and 2) "We're continuing our Azure migration." also clearly not working.

So needless to say, if you depend on GitHub for critical business operations, you need to start thinking about what a world without GitHub looks like for your business and start working your way toward that. I know my confidence in GitHub's engineering leadership is at rock bottom.

There’s plenty of alternatives, but people continue to stay. Therefore, it’s not as bad as you think it is.
Vibe coding and it's consequences.

"The evidence is clear: Either you embrace AI, or get out of this career." -Github CEO

"Sooner than later, 80% of the code is going to be written by Copilot. And that doesn’t mean the developer is going to be replaced." -Github CEO

The worst part is that users still stay and take the abuse.
(comment deleted)
looking forward to the `addressing-githubs-recent-availability-issues-3` news post
Microsoft products are so human, they stop working weekly as if they're observing some sort of sabbath ...
Does github not do any kind of blue/green rollouts or what