This is getting ridiculous. One particularly concerning thing I’m seeing is that pull requests on both the web UI and API aren’t reflecting all commits or branch changes consistently. It would be very easy to merge something without realizing you’re not actually reviewing the full diff.
Incident with Pull Requests, Issues, Git Operations and API Requests
161–170 of 221 posts
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#162Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#163Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#164They’re trying to scale from 1 billion commits last year to over 14 billion this year. I have zero desire to try and manage that scaling. Basically being DDOS’d by agents all day now.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#165I know it’s super fun to shit on GitHub and everyone’s favorite thing to say is “build a competitor!” They’re trying to scale from 1 billion commits last year to over 14 billion this year. I have zero desire to try and manage that scaling. Basically being DDOS’d by agents all day now. https://x.com/kdaigle/status/2040164759836778878
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#166Earlier quoted context omitted.
Is this growth in resource usage or growth in revenue? Because those numbers aren't necessarily coupled. I.e most action runners are free
usage
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#167is it me or ever since AI coding became the norm, there have been way more outages with otherwise reliable services? I get downtime on Supabase every few weeks. Even Cloudflare. And now Github
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#168Earlier quoted context omitted.
GH was acquired by microsoft some eight years ago. It has been working quite well until recently. People may have had complaints about functionality, features, commercial issues, but the thing used to at least have a decent uptime until recently.
Has nothing to do with Microsoft acquisition... AI usage has increased demand and load. More PRs, more Action runners, more of everything firing. GitHub just wasn't ready for the scale and are now having issues catching up with it as it continues to increase exponentially.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#169https://isgithubcooked.com Normally I defend GH in the comments of these incidents but it’s been an impressively bad month by their standards, even when you filter for critical components filter out sev-2’s and 3’s.
Of all the sites/graphs I've seen of GH outages, this one is the most striking IMO: https://damrnelson.github.io/github-historical-uptime/ Unfortunately, it doesn't look like it's being updated with new data. But it wouldn't look any better for GH if it was.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#170Earlier quoted context omitted.
Here is a provocative thought - maybe these are the so-called "better designs" from LLMs? It's not like writing English sentences is some huge secret you are sitting on that no one else knows.
> It's not like writing English sentences is some huge secret you are sitting on that no one else knows. I'd actually say what really makes an excellent engineer stick out among many great engineers, is their ability to communicate clearly and knowing what needs to be communicated vs not, basically being way better at language and communication in general, and they also understand the important of it.