Live data from Hacker News

Incident with Issues and Webhooks – Resolved

githubstatus.com

121–130 of 275 posts

Re: Incident with Issues and Webhooks – Resolved

#121
post #96

The goals for code-versioning as they existed decades back, might be sliding into irrelevance now. Code is no longer a direct work artifact from humans, as it used to be. Back in the day, people wanted to persist their code and it's changes, because code was hard to write and test. People didn't use a versioning system for their compiled binaries though, because it was a machine output and can be created from source…

Flawed reasoning all around. Machine code and object code will look the same given the same source code, target platform, compilation and linkin params etc. How is AI-Slop-Code even close to that?

Re: Incident with Issues and Webhooks – Resolved

#124

Github has published some incredible usage rate increase numbers, which they ascribe to the rise of agentic coding. At some point, they are going to have to change rate limits, cut free-tier usage, or find some other path to reducing load. It's clear that their infrastructure can't keep up with this significant increase, and it's unlikely that they're going to just absorb the increased costs themselves. Very curious…

Huh, so vibe coding really is the reason GitHub has been down so much lately!

Re: Incident with Issues and Webhooks – Resolved

#125
post #33
post #3

Earlier quoted context omitted.

_Usually_ the blast radius isn't "GH is down globally across all functionality". So it can work for you while still being either down for other regions, or at least degraded.

Pushing commits over SSH is often the most "reliable" thing, though you can get some fun situations where a commit is pushed and runners never ran, causing downstream FUN eventually.

I’ve seen this behaviour but IMO it’s a fatal design flaw of Actions. It shouldn’t be possible.

Re: Incident with Issues and Webhooks – Resolved

#126

This is genuinely pathetic. I wish I could do my job this poorly and still be employed.

Keep in mind that it's easy to call someone else incompetent whenever their thing doesn't work, but we have no full idea what's going on behind the scenes. They could be very competent people in an unwinnable situation (like being forced to use Azure).

Re: Incident with Issues and Webhooks – Resolved

#128
post #77

Earlier quoted context omitted.

From the GitHub COO on April 3rd: Platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.) GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week in 2025, and now 2.1B minutes so far this week. So we're pushing incredibly hard on more CPUs, scaling services, and strengthening G…

This is extremely interesting how fast this happened. Either AI use surged massively in the last quarter, or this is a very sneaky move by Anthropic. Looking at my own stats, I don't think I'm using Claude Code much more than I used to, but my commits have gone way up. I have a feeling they've tuned the models recently to commit more often, which gives the illusion of more work being done.

I don't think commits per se puts pressure on the infrastructure.

More likely pulls and pushes, and, naturally, the ci minutes they identify as the main issue.

Re: Incident with Issues and Webhooks – Resolved

#129

Earlier quoted context omitted.

We should make an alternative git site, but how to acquire users?

What do you need users for? GH is not a social network

I don't know. Everyone seems to be using GitHub only because everyone else is using GitHub. Apparently that's important somehow. Me, I use "git init"

Re: Incident with Issues and Webhooks – Resolved

#130
post #96

The goals for code-versioning as they existed decades back, might be sliding into irrelevance now. Code is no longer a direct work artifact from humans, as it used to be. Back in the day, people wanted to persist their code and it's changes, because code was hard to write and test. People didn't use a versioning system for their compiled binaries though, because it was a machine output and can be created from source…

Flawed reasoning all around. Machine code and object code will look the same given the same source code, target platform, compilation and linkin params etc. How is AI-Slop-Code even close to that?

"looking same" is not the requirement. "Working same" is. With proper test harness, the generated code can be controlled to "work the same".
Post reply on HN