63 comments

[ 4.6 ms ] story [ 62.7 ms ] thread
Right in the middle of a huge rebase. Great!
How does an outage of a remote repo affects your local rebase.
(comment deleted)
Good thing I always commit directly to the main branch.
(comment deleted)
Guess it's time to embrace AI.
Props to Github for having an accurate status page. AWS and Google should take note.
As someone who is partially responsible for supporting github at a very large organization, no it isn't. At least not until the incident is at least 30m old if ever.
GitHub gives everyone an extra long lunch.
(comment deleted)
I guess they let copilot review their code
After writing it :)
No excuse. git-send-email out and stop slacking :)
Not a good look when they're heavily pushing AI agents.
I’ll be waiting expectantly for the post mortem of this. How ironic would it be if this issue was caused by a pull request itself?
This is why I recommend decentralized protocols like radical or I guess I hope that tangled.sh could fix this stuff too.

I am not sure about tangled.sh, I might ask them in their discord about this now y'know.

I didn’t think the code I just merged was that bad
From the CEO's article referenced in that post [1]:

> the rise of AI in software development signals the need for computer science education to be reinvented as well.

> Teaching in a way that evaluates rote syntax or memorization of APIs is becoming obsolete

He thinks computer science is about memorizing syntax and APIs. No wonder he's telling developers to embrace AI or quit their careers if he believes the entire field is that shallow. Not the best person to take advice from.

It's also hilarious how he downplays fundamental flaws of LLMs as something AI zealots, the truly smart people, can overcome by producing so much AI slop that they turn from skeptics into ...drumroll... AI strategists. lol

[1]: https://ashtom.github.io/developers-reinvented

Give your best estimate on how much dollar value of creation is wasted every hour GitHub PRs are down
(comment deleted)
(comment deleted)
This is strange: I was just having issues with Pull Requests on BitBucket too. Coincidence, actually?
It's all a central svn in AWS