Another day, another GitHub incident (githubstatus.com)

[delayed]

This explains why it took GitHub 5+ minutes to acknowledge a push to a PR branch.

Too many projects working on fixing (merging PRs and building patched images) the latest PHP incident? Causing a DoS on Github would be a quite "funny" side-effect of this whole thing.

Has any other service been affected as hard as GitHub by this wave of AI-generated code?

So much stuff is down today for php fixes. I can't even do Duolingo!

[dead]

Even with all the incidents, this month is tracking to be the best month in terms of # of new orgs using Github: https://bloomberry.com/data/github/

Luckily nobody has to do critical updates right now

Time to push straight to master then

I think explicitly Delays for Pull Requests and Webhook deliveries would be a more accurate and helpful title.

The engineers they "replaced" with AI aren't coming back...

oh github outage . all is well in the world.

I switched all my repos to Cursor Origin when the last outage happened a couple of days ago. Origin is fast. It’s comparable to moving from Jira to Linear. I highly recommend everyone try it.

I had to move my CI to Buildkite and am also running a self-hosted windows runner, but other than that, most services I used such as cloudflare workers and code rabbit work with Origin. Claude was essential in getting all work in progress PRs reopened as well.