Incident with Github.com [resolved]

Post by materielle » Mon, Aug 17, 2026, 2:53 PM UTC

chilmers wrote: post #165

rand_r wrote: post #76

Earlier quoted context omitted.

That's fine, but rate limiting is a solved problem at this point. They need to rate-limit free accounts and be realistic about their limits instead of letting the system fail.

Free (and non-free) accounts are already rate limited. The likely problem is that individual accounts/repos rarely hit those limits, instead the explosive demand is due to a massive growth in the number of small, individual projects being creatd.

Post by hosh » Mon, Aug 17, 2026, 2:53 PM UTC

MoreQARespect wrote: post #250

noosphr wrote: post #134

Earlier quoted context omitted.

Luckily we already have a distributed version control system that can take over github: https://fossil-scm.org/home/doc/trunk/www/index.wiki I suppose people can use git too if they ever figure out how to send emails from a dedicated client.

There are plenty of alternatives for git hosting. The last thing which needs to be migrated before we get an exodus off this vibe coded monstrosity is reputation (i.e. github stars) which are inherently sticky.

Post by mitchjj » Mon, Aug 17, 2026, 2:54 PM UTC

latchkey wrote: post #123

beardedetim wrote: post #15

We're starting to have the conversation of "do we need to replace GitHub as our CI/CD pipeline?" No idea if/when we decide to pull that bandaid but I think once we can't merge a hot fix into main because of GH being down, it'll be a big org push to replace it. What's everyone else using? Self hosted Gitlab? Gitea?

blacksmith.sh just raised tens of millions on the core premise that self-hosting CI/CD is hard [0]. they've had multiple outages in the last week, so i guess they are proving themselves correct. in practice, giving ssh/sudo to AI (codex) and telling it to setup ephemeral self-hosted runners on your own host VM (qemu), takes about 30 minutes and works extremely well. it bangs out all the shell scripts. moved my own bu…

Post by Aachen » Mon, Aug 17, 2026, 2:54 PM UTC

Laurel1234 wrote: post #346

Aachen wrote: post #225

Earlier quoted context omitted.

Huh, they usually do? I'm not a full-time developer though so I'm surely biased towards doing the obvious quick fixes or already-discussed things, but discussing how to solve a problem before throwing something at the wall seems like the normal thing to do for me Or is their point about abandoned projects where the dev never clicks release after merging, or even never merges?

The point is you can't ship shit during an outage.

Post by BowBun » Mon, Aug 17, 2026, 2:54 PM UTC

Aachen wrote: post #225

fzumstein wrote: post #190

Funny enough, I received a marketing email from GitHub during the outage with the following subject: "What if every pull request you started actually shipped"

Huh, they usually do? I'm not a full-time developer though so I'm surely biased towards doing the obvious quick fixes or already-discussed things, but discussing how to solve a problem before throwing something at the wall seems like the normal thing to do for me Or is their point about abandoned projects where the dev never clicks release after merging, or even never merges?