Delays for Pull Requests and Webhook deliveries
Posted by bearsyankees 1 day ago
Comments
Comment by EduardoBautista 22 hours ago
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.
Comment by lexoj 23 hours ago
Time to push straight to master then
Comment by feukon 23 hours ago
Has any other service been affected as hard as GitHub by this wave of AI-generated code?
Comment by AshleyGrant 1 day ago
This explains why it took GitHub 5+ minutes to acknowledge a push to a PR branch.
Comment by comrade1234 23 hours ago
So much stuff is down today for php fixes. I can't even do Duolingo!
Comment by keraf 1 day ago
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.
Comment by AznHisoka 23 hours ago
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/
Comment by microsoftedging 23 hours ago
I think explicitly Delays for Pull Requests and Webhook deliveries would be a more accurate and helpful title.
Comment by nope1000 23 hours ago
Luckily nobody has to do critical updates right now
Comment by aussieguy1234 22 hours ago
The engineers they "replaced" with AI aren't coming back...
Comment by Hamuko 1 day ago
Everyone trying to build a new PHP-based container at the same time?
Comment by dominotw 22 hours ago
oh github outage . all is well in the world.
Comment by pkaler 23 hours ago
[dead]