Incident with Pull Requests, Issues, Git Operations and API Requests • Hacker News Board

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#201

Post by hugey010 » Thu, May 28, 2026, 1:09 AM UTC

embedding-shape wrote: post #56

angrydev wrote: post #48

Earlier quoted context omitted.

Compared to near unusable pages that large organizations produce, yes this page is highly effective at conveying information. Who cares how it was produced?

> Who cares how it was produced? Well, we're at least two people who care, since we were conversing about how good/bad the webdesign is, then you jumped in here :) If you don't care, why bother to reply to people who seemingly do care? What kind of conversation are you expecting here, "Yeah, do tooo"? :|

Could you explain why you care?

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#202

Post by [deleted] » Thu, May 28, 2026, 1:24 AM UTC

gen220 wrote: post #177

rsyring wrote: post #159

Earlier quoted context omitted.

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.

FWIW, I'm not convinced that chart is necessarily an accurate representation of pre-acquisition reality. It would really surprise me if GitHub did not have a single sev-0 pre-acquisition, but it wouldn't surprise me if they were not formally captured and reported in a format that would make its way into their current status page's database.

[deleted]

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#203

Post by applfanboysbgon » Thu, May 28, 2026, 2:41 AM UTC

hugey010 wrote: post #201

embedding-shape wrote: post #56

Earlier quoted context omitted.

> Who cares how it was produced? Well, we're at least two people who care, since we were conversing about how good/bad the webdesign is, then you jumped in here :) If you don't care, why bother to reply to people who seemingly do care? What kind of conversation are you expecting here, "Yeah, do tooo"? :|

Could you explain why you care?

A lack of effort put into presentation is a signal for low quality. In the past, this might've manifested in using default Wordpress templates, and now it manifests as stock LLM templates instead. Can you make high quality content and present it on a stock template? Sure, you can, but without any prior reason to believe that you put more effort into the content than the template, I'm liable to believe the content is LLM-generated slop as well and therefore untrustworthy and not worth my time.

In this case, it appears more effort was put into content than presentation, which is a possibility and the creator is in the comments saying as such, but humans operate on heuristics by default. The majority of sites that look like this have been a complete waste of my time and I usually just click away at this point.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#204

Post by lbindreiter » Thu, May 28, 2026, 7:03 AM UTC

drdrey wrote: post #90

olmo23 wrote: post #44

Earlier quoted context omitted.

What really grinds my gears is how easy it is to get better designs out of LLMs. But if you don't ask, you get the default.

as someone who doesn't know how to get better design out of LLMs, can you elaborate?

Also check out https://impeccable.style/, it's really good

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#205

Post by carreau » Thu, May 28, 2026, 9:19 AM UTC

Reminder that after more than a month, many repos _still_ don't show all PRs and Issues https://github.com/orgs/community/discussions/193463

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#206

Post by rldjbpin » Thu, May 28, 2026, 9:52 AM UTC

among all the recent incidents, this was probably the first time i experienced any service disruption.

even comparing branches were giving 500 in the web ui. even github copilot in their new session limits now also mention if github is going through an incident, which is plainly comical.

fun times!

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#207

Post by chris_money202 » Thu, May 28, 2026, 10:11 AM UTC

skywhopper wrote: post #189

chris_money202 wrote: post #62

Earlier quoted context omitted.

Yes, because that caused the usage of the services to skyrocket, GitHub runs on Azure and Azure is experiencing capacity strain due to AI, so GitHub's services are struggling to auto-scale

GitHub’s data architecture (lots and lots of projects in a hierarchical distribution with immutable, highly transaction-based data elements) ought to be easily shardable to allow for massive scale-out. Especially a decade after acquisition by Microsoft. Even a major increase in activity (which was surely predicted internally years ago, given the marketing around AI) should be easily handled by a company with their re…

Microsoft has been letting GitHub operate independently since up to very recently. Seems to imply the problems could be systemically GitHub’s and Microsoft is now stepping in and correcting the ship.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#208

Post by My_Name » Thu, May 28, 2026, 10:32 AM UTC

I'm finding this amusing because today, I am in the process of removing all my code from GitHub and cloning it to a local Git that has a webhook to a local releases server.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#209

Post by My_Name » Thu, May 28, 2026, 10:53 AM UTC

vinnymac wrote: post #77

taintlord223 wrote: post #33

Earlier quoted context omitted.

The UI of that page is so nice, should build a github competitor. The user profile / contributions and PR UX is pretty much the entire "hub" product since git is a fully separate offline app.

I’m actively working on an alternative Frontend for Forgejo at the moment, completely self hostable, free, and open source. Moving everything from GitHub to Forgejo and Tangled for now. These outages haven’t effected me for the past month because of this.

I'm deleting my GitHub repos today (been planned for a bit) in favour of a local Forgejo Git. I also have not experienced any service disruption since I migrated well over a month ago.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#210

Post by fg137 » Thu, May 28, 2026, 11:08 AM UTC

Robdel12 wrote: post #164

I 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

> I have zero desire to try and manage that scaling.

Last time I checked, this is called "doing their job".

You are free to choose what company you want to work for, but for github, if they are offering the services, often as paid services, they have an obligation to keep things running which is called SLA. Otherwise people will leave (and are leaving)