News for hackers. Stuff that matters.
Re:Incident with Pull Requests, Git Operations and Issues by thesdev on Wednesday November 04, 2026 @05:09AM (#50363449)
Finally a GitHub outage during European workday. Yaaay.
Re:Incident with Pull Requests, Git Operations and Issues by nope1000 on Wednesday November 04, 2026 @06:58AM (#50364379)
Although it is lunchtime :/
Re:Incident with Pull Requests, Git Operations and Issues by y-curious on Wednesday November 04, 2026 @08:33AM (#50365308)
Isn’t most of the European workday lunch time? :P

I joke, the QoL is really nice

Re:Incident with Pull Requests, Git Operations and Issues by esher on Wednesday November 04, 2026 @05:10AM (#50363463)
Again and again?
Re:Incident with Pull Requests, Git Operations and Issues by anon7000 on Wednesday November 04, 2026 @05:23AM (#50363556)
That is how explosive demand growth works after all. They just aren’t keeping up with increasing capacity or rate limiting people
Re:Incident with Pull Requests, Git Operations and Issues by crote on Wednesday November 04, 2026 @05:57AM (#50363829)
GitHub is down only on days ending in -day.
Re:Incident with Pull Requests, Git Operations and Issues by chinathrow on Wednesday November 04, 2026 @05:13AM (#50363480)
git clone works, git checkout not so much.
Re:Incident with Pull Requests, Git Operations and Issues by computerfriend on Wednesday November 04, 2026 @05:34AM (#50363647)
Unauthenticated fetches seem ok. Not sure what you mean about git checkout, it's purely local.
Re:Incident with Pull Requests, Git Operations and Issues by sognetic on Wednesday November 04, 2026 @05:14AM (#50363491)
Can't even pull no more using my key. That's a new low, I'm used to the website being janky nowadays but this is seriously essential
Re:Incident with Pull Requests, Git Operations and Issues by ayhanfuat on Wednesday November 04, 2026 @05:27AM (#50363595)
At least they have a very clear error message so you know what is going on.

> [email protected]: Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

Re:Incident with Pull Requests, Git Operations and Issues by chinathrow on Wednesday November 04, 2026 @05:41AM (#50363701)
That's standard git, not coming from GH.
Re:Incident with Pull Requests, Git Operations and Issues by b1tshift on Wednesday November 04, 2026 @05:40AM (#50363694)
Just rolled new keys and though I'm going crazy that it's not working
Re:Incident with Pull Requests, Git Operations and Issues by Insimwytim on Wednesday November 04, 2026 @09:32AM (#50366057)
They removing some key types today, as was mentioned above [1][2], maybe you were hit by that.

  November 4, 2026: We’ll have a brownout of the removal of the ssh-rsa signature type (i.e., RSA keys using SHA-1) and the diffie-hellman-group-exchange-sha256 key exchange algorithm.
[1] https://news.ycombinator.com/item?id=50363936

[2] https://github.blog/changelog/2026-09-22-security-improvemen...

Re:Incident with Pull Requests, Git Operations and Issues by igleria on Wednesday November 04, 2026 @05:19AM (#50363515)
Can't they just... sell github back like when the germans sold the nuclear plant back to mr burns?
Re:Incident with Pull Requests, Git Operations and Issues by solyin on Wednesday November 04, 2026 @05:25AM (#50363576)
As of 2026-11-04T10:25:34Z the domain MicrosoftPleaseGiveGithubToGoogle.com is still unclaimed.
Re:Incident with Pull Requests, Git Operations and Issues by selectnull on Wednesday November 04, 2026 @05:32AM (#50363625)
Yes, really at this point it would be best if MS sold Github to Google and they kill it within a year.
Re:Incident with Pull Requests, Git Operations and Issues by zbentley on Wednesday November 04, 2026 @08:49PM (#50374042)
Ah yes, Google, known good steward of acquired companies’ projects and notable luminary in the developer tooling and workflow space.

Wait…

Re:Incident with Pull Requests, Git Operations and Issues by eknkc on Wednesday November 04, 2026 @05:23AM (#50363553)
Our deploys are tied to GitHub actions and it is becoming a liability at this point. What alternatives do people use? I mean for FOSS there are some decent stuff but we need a reliable provider for private repos.
Re:Incident with Pull Requests, Git Operations and Issues by misswaterfairy on Wednesday November 04, 2026 @05:28AM (#50363599)
Genuine question: if you're hosting private repos, is self-hosting an option?

Gitea Enterprise would be worth looking at.

https://about.gitea.com/products/gitea-enterprise/

Re:Incident with Pull Requests, Git Operations and Issues by eknkc on Wednesday November 04, 2026 @05:45AM (#50363731)
Honestly, not really wanna deal with self hosting it. Would rather pay for a decent service at this point.
Re:Incident with Pull Requests, Git Operations and Issues by import on Wednesday November 04, 2026 @05:48AM (#50363753)
There is already a blacksmith sh if you don't want to selfhost your runners. Or codeberg as a full solution if I am not mistaken.
Re:Incident with Pull Requests, Git Operations and Issues by michaelbuckbee on Wednesday November 04, 2026 @05:56AM (#50363820)
+1 for Blacksmith. You need to have a Github org to use it as it won't work on personal accounts, but it feels like a magic want that just makes runners 2x as fast.

I have it for all my stuff (dozens of repos and hundreds of PRs/builds per week) and it's only once in the last year that I've exceeded the free resource levels. I don't know if it's just extra capacity or they're burning VC dollars in the hopes of inspiring posts like this, but either way I feel like I'm taking advantage of them at this point.

Re:Incident with Pull Requests, Git Operations and Issues by booi on Wednesday November 04, 2026 @05:28PM (#50372376)
But doesn't Blacksmith piggy back off of the Github Actions control plane? Outages will just spread to Blacksmith
Re:Incident with Pull Requests, Git Operations and Issues by crote on Wednesday November 04, 2026 @05:59AM (#50363841)
Codeberg only allows F/LOSS software, for most companies that's a dealbreaker.
Re:Incident with Pull Requests, Git Operations and Issues by tcfhgj on Wednesday November 04, 2026 @07:53AM (#50364875)
Private projects usually are not owned by companies
Re:Incident with Pull Requests, Git Operations and Issues by crote on Wednesday November 04, 2026 @12:41PM (#50368940)
Your proprietary personal hobby project doesn't need an entire publicly-accessible Forge, it can just live on your local drive or home server. It is also not critical enough that GitHub occasionally being down is a big deal.

If you're looking for a publicly-accessible Forge SaaS for your private repos and are willing to pay for it, you are almost certainly a company developing proprietary software.

Re:Incident with Pull Requests, Git Operations and Issues by pelagicAustral on Wednesday November 04, 2026 @05:30AM (#50363611)
My deployments are tied to their container registry, so I'm equally screwed... Been thinking of going back to Dokku, I started working on a third wrapper around Dokku (yeah, I've literally done this twice already), and then self-host and self-provision... I honestly thinking seriously about this.
Re:Incident with Pull Requests, Git Operations and Issues by saturn_vk on Wednesday November 04, 2026 @05:42AM (#50363712)
Self-hosted Forgejo with a bunch of runners might also be interesting for you. The workflow syntax is _almost_ identical to the github one.
Re:Incident with Pull Requests, Git Operations and Issues by import on Wednesday November 04, 2026 @05:47AM (#50363739)
gitea is amazing.
Re:Incident with Pull Requests, Git Operations and Issues by raddan on Wednesday November 04, 2026 @06:25AM (#50364098)
Seconded. Also very easy to set up. I’ve been running it for years, along with webhooks to kick off testing and website deployment jobs. I especially like the swagger browser that generate API calls for you to try in curl. I use the API pretty extensively.
Re:Incident with Pull Requests, Git Operations and Issues by rozularen on Wednesday November 04, 2026 @05:52AM (#50363783)
self hosted forgejo has been my saviour. im thinking in acquiring a new NUC server to increase compute and storage to my homelab to add some new runners
Re:Incident with Pull Requests, Git Operations and Issues by myaccountonhn on Wednesday November 04, 2026 @06:01AM (#50363853)
Post receive hook on a bare git repo with gitolite for access control.
Re:Incident with Pull Requests, Git Operations and Issues by jelder on Wednesday November 04, 2026 @06:40AM (#50364243)
Git itself usually works, but we gave up on GHA and use https://www.rwx.com/ for tests, previews, and deployments. It’s 2x to 10x faster than GitHub Actions and testing uncommitted changes on real CI infrastructure is a total game changer.
Re:Incident with Pull Requests, Git Operations and Issues by embedding-shape on Wednesday November 04, 2026 @07:28AM (#50364655)
You don't even have to migrate off GitHub if you don't want to.

Begin by refactoring the deployments so they're driven by checked in shellscripts, that accepts a git reference to deploy (prefer immutable commit SHAs over mutable branches/tags). Make it use the stuff it already has checked in, and make the actual GitHub Actions stuff as small and concise as possible, ideally each "run" should just call a shellscript with the git reference.

Then move so the deploys happen not on GitHub Actions itself, but on a "intermediate deploy host" that has the source code and access to the credentials you need, and make this host have one secure entrypoint, where someone (or something) can enter and run shellscripts, after pushing their code as a normal git push. Then switch so the deploys from GitHub Actions instead use this new host to do the deploys. Lock down this host hard.

When GitHub and/or GitHub Actions go down, the developer responsible for deploying stuff, should be able to get temporary git and ssh access to this host, can push any git data straight to the host, and their user on this host can run the deploy scripts. Keep in mind that nothing in your deployment process should depend on stuff that isn't also available on this "deploy host", if you have multiple synced repositories and so on.

Now things mostly work the same as people are used to, with the added benefit that when things go down again (like next week), you'll still be able to continue to deploy stuff.

I've done this refactor/migration for tens of companies in the last year, more or less following this exact template for all of them, with no issues reported from either of them, but lots of praise :)

Re:Incident with Pull Requests, Git Operations and Issues by SkiFire13 on Wednesday November 04, 2026 @07:33AM (#50364707)
Some of our deploys use CircleCI instead, but they were still broken because they couldn't checkout from Github.
Re:Incident with Pull Requests, Git Operations and Issues by bonetruck on Wednesday November 04, 2026 @07:46AM (#50364810)
Forgejo backed by Woodpecker CI running on Kubernetes (Talos) has been amazing! Ditch Github Actions syntax for the simplicity of Woodpecker and containers. You'll thank me later.
Re:Incident with Pull Requests, Git Operations and Issues by paaloeye on Wednesday November 04, 2026 @09:25AM (#50365957)
How do you run Docker containers inside your K8S? Let’s say you need a test database or test ClickHouse???
Re:Incident with Pull Requests, Git Operations and Issues by NewJazz on Wednesday November 04, 2026 @10:07AM (#50366630)
[delayed]
Re:Incident with Pull Requests, Git Operations and Issues by stack_framer on Wednesday November 04, 2026 @07:56AM (#50364899)
We use GitLab where I work. The only problem is it calls pull requests "merge requests," and I don't think I'll ever get used to saying "MR" instead of "PR."
Re:Incident with Pull Requests, Git Operations and Issues by hhh on Wednesday November 04, 2026 @08:09AM (#50365055)
I have the opposite
Re:Incident with Pull Requests, Git Operations and Issues by jaapz on Wednesday November 04, 2026 @08:33AM (#50365298)
Why are all you github people pulling on your requests?

I am requesting to merge my changes into the main branch.

Re:Incident with Pull Requests, Git Operations and Issues by dutchbart on Wednesday November 04, 2026 @09:58AM (#50366463)
Or you are requesting me to pull your changes into my branch.
Re:Incident with Pull Requests, Git Operations and Issues by crote on Wednesday November 04, 2026 @12:36PM (#50368874)
Because in the good old days when git was still distributed, a merge often started with sending someone an email to obtain your newly-coded commits via `git pull`ing your "gpu-drivers-for-linus" branch from some URL pointing to your personal GitWeb install. In other words: it was a request to pull your code.

Similarly: Why are the Gitlab people so happy to merge? Where is my "Rebase Request", "Squash Request", or "Cherry-pick Request"?

Re:Incident with Pull Requests, Git Operations and Issues by chrisweekly on Wednesday November 04, 2026 @01:53PM (#50369926)
good bit of lore.

related tidbit: in git, "pull" is basically shorthand for "fetch + merge".

Re:Incident with Pull Requests, Git Operations and Issues by ajasmin on Wednesday November 04, 2026 @05:56PM (#50372623)
You can still do this with GituHub pull the PR branch locally, read the code, try thing out, rebase on main…
Re:Incident with Pull Requests, Git Operations and Issues by delf on Wednesday November 04, 2026 @08:04AM (#50364993)
I self-host with GitSocial.

https://gitsocial.org/

Re:Incident with Pull Requests, Git Operations and Issues by Roark66 on Wednesday November 04, 2026 @09:25AM (#50365962)
This is exactly why I don't understand companies (like some of my clients) that move from self hosted Jenkins to GH Actions.

You're literally replacing a well designed resilient system with a single point of failure run by a different company...

Re:Incident with Pull Requests, Git Operations and Issues by Chris2048 on Wednesday November 04, 2026 @10:31AM (#50367018)
> a well designed resilient system

Wait, Jenkins?

Re:Incident with Pull Requests, Git Operations and Issues by iamjake648 on Wednesday November 04, 2026 @02:06PM (#50370088)
Like with all things, it really depends on having someone competent stand it up and run it. I think we've already reached the point that this is totally worth it for mid-sized companies as opposed to giving MS money for GHA.
Re:Incident with Pull Requests, Git Operations and Issues by hiccuphippo on Wednesday November 04, 2026 @10:53AM (#50367369)
I get to tell my manager it's github's fault.
Re:Incident with Pull Requests, Git Operations and Issues by shimms on Wednesday November 04, 2026 @09:29AM (#50366006)
Buildkite with self hosted runners
Re:Incident with Pull Requests, Git Operations and Issues by maccard on Wednesday November 04, 2026 @01:35PM (#50369681)
Which is 4x the price of github, _plus_ the cost of the runners on top of it.

It's a great service though

Re:Incident with Pull Requests, Git Operations and Issues by karolist on Wednesday November 04, 2026 @10:01AM (#50366517)
Self hosted Jenkins, been working wonderfully.
Re:Incident with Pull Requests, Git Operations and Issues by maratc on Wednesday November 04, 2026 @11:37AM (#50368093)
I use Jenkins too, however any pipeline starts by checkout from github, so it failed this morning just the same.
Re:Incident with Pull Requests, Git Operations and Issues by karolist on Wednesday November 04, 2026 @11:48AM (#50368255)
Same for me, ssh access was intermittent, but at least I have reliable local builds when GitHub actions is out but access works. With AI running Jenkins is not that hard. I build large cuda containers so cost alone ruled out hosted builds for my usecase. There's a bit of update churn but nothing broke so far. I ran around 2000 builds last year. I run it on epyc 7v12 128gb ddr4 host.
Re:Incident with Pull Requests, Git Operations and Issues by icy on Wednesday November 04, 2026 @10:41AM (#50367184)
We're shipping private repos for Tangled very soon (tangled.org). Shoot me an email anirudh@!
Re:Incident with Pull Requests, Git Operations and Issues by fauzanhilmi on Wednesday November 04, 2026 @05:24AM (#50363565)
For a moment I thought my ssh key got breached. Fricking hell Github!
Re:Incident with Pull Requests, Git Operations and Issues by dude250711 on Wednesday November 04, 2026 @05:33AM (#50363638)
These days, perhaps, normal undisrupted operation should start counting as an incident...
Re:Incident with Pull Requests, Git Operations and Issues by jonathanbull on Wednesday November 04, 2026 @05:37AM (#50363665)
Re:Incident with Pull Requests, Git Operations and Issues by cashbreaker on Wednesday November 04, 2026 @05:42AM (#50363710)
I was thinking I'm going crazy with me ssh keys not working on both of my machines.
Re:Incident with Pull Requests, Git Operations and Issues by techterrier on Wednesday November 04, 2026 @05:48AM (#50363750)
https is working still!

git -c credential.helper= -c 'credential.helper=!gh auth git-credential' pull https://github.com/myorg/my-repo.git

Re:Incident with Pull Requests, Git Operations and Issues by gumbojuice on Thursday November 05, 2026 @02:09AM (#50376086)
Surprisingly my AI reverted to exactly this, and I almost didn't notice until I had to review a colleague's PR and the merge button didn't work.
Re:Incident with Pull Requests, Git Operations and Issues by larsnystrom on Wednesday November 04, 2026 @05:44AM (#50363720)
Why haven’t they asked an AI agent to fix all their bugs yet? /s
Re:Incident with Pull Requests, Git Operations and Issues by refactor_master on Wednesday November 04, 2026 @05:53AM (#50363788)
Prompting the wrong things is just a skill issue.
Re:Incident with Pull Requests, Git Operations and Issues by Ampersander on Wednesday November 04, 2026 @08:00AM (#50364951)
Why does anyone even use Github anymore? Just generate a better forge with AI
Re:Incident with Pull Requests, Git Operations and Issues by feukon on Wednesday November 04, 2026 @05:45AM (#50363729)
The day GitHub will no longer be free is approaching... they just can't support the abnormal amount of things being pushed rn
Re:Incident with Pull Requests, Git Operations and Issues by crote on Wednesday November 04, 2026 @05:56AM (#50363811)
For most people here GitHub is already a paid platform. Our companies rely on it as a core part of our development workflows, and we pay a decent bunch of money for it. If it was only the free part of GH having issues, it wouldn't get even remotely near this kind of exposure.

Developers are expensive. If I can't ship a feature on time because GitHub issues keeps forcing me to switch to different tasks to work around git/PR/ticket/Actions downtime, then that costs my company real money - despite us not being the source of the AI DDoS that GitHub has happily been welcoming.

To me, the situation is very simple: either 1) rein in the AI deluge, or 2) isolate paying customers from it, or we'll move to an alternative.

For businesses the current state of unreliability would be unacceptable if it was completely free, the fact that it is actually paid just adds insult to injury.

Re:Incident with Pull Requests, Git Operations and Issues by rarisma on Wednesday November 04, 2026 @05:48AM (#50363754)

       - - >  i wake up - -
       |                  |
       |                  V
       github has an outage
Re:Incident with Pull Requests, Git Operations and Issues by dodslaser on Wednesday November 04, 2026 @08:40AM (#50365376)
Do you fall asleep every time GitHub has an outage? Are you narcoleptic?
Re:Incident with Pull Requests, Git Operations and Issues by shepherdjerred on Wednesday November 04, 2026 @12:01PM (#50368442)
You have it wrong. GitHub goes down because they fall sleep
Re:Incident with Pull Requests, Git Operations and Issues by binsquare on Wednesday November 04, 2026 @09:31AM (#50366048)
A manager might say you need to stop waking up.
Re:Incident with Pull Requests, Git Operations and Issues by GrantMoyer on Wednesday November 04, 2026 @09:39AM (#50366157)
This diagram has a couple of interpretations depending on whether or not you work at GitHub.
Re:Incident with Pull Requests, Git Operations and Issues by Chris2048 on Wednesday November 04, 2026 @10:30AM (#50366998)
Perhaps they are a process/thread?
Re:Incident with Pull Requests, Git Operations and Issues by gib444 on Wednesday November 04, 2026 @12:39PM (#50368915)
[delayed]
Re:Incident with Pull Requests, Git Operations and Issues by sigmarule on Wednesday November 04, 2026 @09:13PM (#50374241)
All will be solved by tomorrow!
Re:Incident with Pull Requests, Git Operations and Issues by lta on Wednesday November 04, 2026 @02:47PM (#50370574)
It must be Tuesday, that's why
Re:Incident with Pull Requests, Git Operations and Issues by grishka on Wednesday November 04, 2026 @05:57AM (#50363826)
I managed to push a commit over ssh but then the client threw an error before the push fully completed. I can see the commit on the web, but my client still thinks it isn't pushed. And now when I try to fetch I get "access denied" after a long wait, which is scary. I first thought something got hacked.

Maybe they need a better AI model for their vibe coding. That'll fix everything, right? At least that's what my friends keep telling me when I say that the free LLMs I played around with a bit are incredibly dumb.

Re:Incident with Pull Requests, Git Operations and Issues by misnome on Wednesday November 04, 2026 @06:00AM (#50363849)
At this point, even when there isn't an incident, push/pull have been so unreliable as to fail about 30% of the time.

I can live with the occasional outage but this is a constant problem.

Re:Incident with Pull Requests, Git Operations and Issues by w3ll_w3ll_w3ll on Wednesday November 04, 2026 @06:08AM (#50363909)
I feel there is a problem with your connectivity or with the Github datacenter you are being routed to. That has not been my experience.
Re:Incident with Pull Requests, Git Operations and Issues by rvz on Wednesday November 04, 2026 @06:02AM (#50363862)
Another incident. Last time we had one was 5 days ago [0]

It's up to you if you want more of this instability. Perhaps you should consider a self-hosted alternative.

[0] https://news.ycombinator.com/item?id=50307843

Re:Incident with Pull Requests, Git Operations and Issues by marvstazar on Wednesday November 04, 2026 @06:02AM (#50363863)
Pretty good timing now that Rails has released a security update :|

https://rubyonrails.org/2026/11/4/Rails-8.0.5.2-and-8.1.4.1-...

Re:Incident with Pull Requests, Git Operations and Issues by malikolivier on Wednesday November 04, 2026 @06:09AM (#50363924)
If your stack is pulling artifacts from GitHub, and this consistently fails during GitHub outage, you can consider having a file-cache in between.

Some of our customers unexpectedly started using the service we're running as a file-cache around GitHub to mitigate GitHub outages.

We wrote about this use case in our blog: https://www.stablebuild.com/blog/protect-your-builds-from-gi...

Re:Incident with Pull Requests, Git Operations and Issues by jaapz on Wednesday November 04, 2026 @08:35AM (#50365327)
Self promotion is generally frowned upon here
Re:Incident with Pull Requests, Git Operations and Issues by juped on Wednesday November 04, 2026 @05:03PM (#50372175)
no, self-promotion is most of the content here, but it has to be somewhat aware of prevailing norms
Re:Incident with Pull Requests, Git Operations and Issues by a-squirrel-comm on Wednesday November 04, 2026 @06:10AM (#50363936)
It looks like today there was maintenance scheduled to deprecate support for certain categories of SSH keys: https://github.blog/changelog/2026-09-22-security-improvemen...

> November 4, 2026: We’ll have a brownout of the removal of the ssh-rsa signature type (i.e., RSA keys using SHA-1) and the diffie-hellman-group-exchange-sha256 key exchange algorithm.

I guess something went sideways.

Re:Incident with Pull Requests, Git Operations and Issues by igleria on Wednesday November 04, 2026 @06:14AM (#50363973)
hey how much do I owe you for this INCREDIBLY important information? This is not sarcasm btw.
Re:Incident with Pull Requests, Git Operations and Issues by a-squirrel-comm on Wednesday November 04, 2026 @06:26AM (#50364112)
nothing :) hope they'll release a statement soon, this is was an assumption on my side, it might be totally wrong. I had intermittent issues with basic git pull/push ops locally so I went to dig a bit. ps: if you do have money to spare, consider donating to the EFF (https://www.eff.org) though B)
Re:Incident with Pull Requests, Git Operations and Issues by igleria on Wednesday November 04, 2026 @06:28AM (#50364127)
thanks a bunch! will do.
Re:Incident with Pull Requests, Git Operations and Issues by DanielHB on Wednesday November 04, 2026 @08:50AM (#50365495)
hah I was wondering why I was getting invalid key errors from github
Re:Incident with Pull Requests, Git Operations and Issues by qtqtqt on Wednesday November 04, 2026 @06:22AM (#50364064)
How to check if one's SSH keys are still compatible?
Re:Incident with Pull Requests, Git Operations and Issues by dist-epoch on Wednesday November 04, 2026 @06:58AM (#50364374)
if any of your SSH key files are bigger than 500 bytes, you should rotate them
Re:Incident with Pull Requests, Git Operations and Issues by SkiFire13 on Wednesday November 04, 2026 @07:31AM (#50364689)
Bigger or smaller?
Re:Incident with Pull Requests, Git Operations and Issues by mschuster91 on Wednesday November 04, 2026 @07:47AM (#50364821)
EC keys should be much smaller... this is only valid for id_rsa SSH keys
Re:Incident with Pull Requests, Git Operations and Issues by anamexis on Wednesday November 04, 2026 @08:38AM (#50365351)
That’s the point.
Re:Incident with Pull Requests, Git Operations and Issues by matja on Wednesday November 04, 2026 @08:49AM (#50365480)
Even mldsa44-ed25519?
Re:Incident with Pull Requests, Git Operations and Issues by pksunkara on Wednesday November 04, 2026 @02:24PM (#50370321)
If this is truly the cause of the outage, then the incident looks like a result of GitHub's own vibecoding instead of the increase in usage.

Disclaimer: I am building a code forge at https://juju.bi

Re:Incident with Pull Requests, Git Operations and Issues by shawabawa3 on Wednesday November 04, 2026 @02:59PM (#50370706)
[delayed]
Re:Incident with Pull Requests, Git Operations and Issues by fredsted on Wednesday November 04, 2026 @06:14AM (#50363970)
Just set up a Gitea instance, pushed my code and switched my deployment script to it. Took 30 minutes. Github pulls still aren't working.
Re:Incident with Pull Requests, Git Operations and Issues by swe_dima on Wednesday November 04, 2026 @06:23AM (#50364083)
Temporary workaround is to do

git config --global url."https://github.com/".insteadOf [email protected]:

so it pushes / pulls using HTTPS

when things are back to normal run:

git config --global --unset url."https://github.com/".insteadOf

Re:Incident with Pull Requests, Git Operations and Issues by alper on Wednesday November 04, 2026 @08:10AM (#50365065)
Same old same old.

What were the 60'000 people exiting Microsoft doing if not improving Github?

Re:Incident with Pull Requests, Git Operations and Issues by colek42 on Wednesday November 04, 2026 @08:50AM (#50365493)
Why do we need centralized CI? We just need a gate to make sure the code passes the right checks before we move the tip.
Re:Incident with Pull Requests, Git Operations and Issues by nalekberov on Wednesday November 04, 2026 @08:57AM (#50365579)
because it's simpler.
Re:Incident with Pull Requests, Git Operations and Issues by falcor84 on Wednesday November 04, 2026 @09:03AM (#50365667)
Well, at the very least, that gate needs to be centralized in some way, right? Unless ... are you suggesting using a blockchain ledger for that?
Re:Incident with Pull Requests, Git Operations and Issues by nalekberov on Wednesday November 04, 2026 @09:10AM (#50365771)
I think blockchain ledger wouldn't be enough, there needs to be AI agents on top of that, that combined with some kind of harness layer, plus, ideally agents gossiping with each other and sometimes fighting with each other to get best results.
Re:Incident with Pull Requests, Git Operations and Issues by colek42 on Thursday November 12, 2026 @02:11PM (#50472588)
The gate does not need to be centralized. But I think it makes it convenient. Look into in-toto. Full disclosure. I am a maintainer of one of the sub-projects. I also maintain cilock.dev which is working on this
Re:Incident with Pull Requests, Git Operations and Issues by icy on Wednesday November 04, 2026 @10:44AM (#50367211)
That's the idea behind Tangled's spindles.
Re:Incident with Pull Requests, Git Operations and Issues by taran_narat on Wednesday November 04, 2026 @09:21AM (#50365916)
The outage was quite short
Re:Incident with Pull Requests, Git Operations and Issues by dankobgd on Wednesday November 04, 2026 @09:26AM (#50365970)
too much slop got them
Re:Incident with Pull Requests, Git Operations and Issues by gophigure on Wednesday November 04, 2026 @09:49AM (#50366293)
What I find problematic, especially for teams that rely on GitOps and GitHub being (relatively) stable, is the fact that GitHub's status page can't be relied on. You arrive at the conclusion, "this must be GitHub," but the status page rejects the notion, and so you go digging. That can lead to a lot of toil and wasted time, in addition to sideways looks paired with comments like, "but status shows green."

A sick person with symptoms is clearly sick, but sometimes they're asymptomatic. That's what the GitHub status page has become. When it's red and showing problems, you know you have problems. When it's all green? You know you MIGHT have problems.

That can make outages like this harder to triage, since reality is a black box.

Re:Incident with Pull Requests, Git Operations and Issues by c0rruptbytes on Wednesday November 04, 2026 @10:30AM (#50366997)
I can imagine a lot of people moving to OCI instead of GitOps
Re:Incident with Pull Requests, Git Operations and Issues by stryan on Wednesday November 04, 2026 @10:35AM (#50367071)
OCI layering on top of running systems a la bootc? or OCI as the desired state storage for CM?
Re:Incident with Pull Requests, Git Operations and Issues by stackskipton on Wednesday November 04, 2026 @11:02AM (#50367511)
SRE here, OCI for storing deployment config information, most of time, Kubernetes manifest files/Helm Charts.
Re:Incident with Pull Requests, Git Operations and Issues by stryan on Wednesday November 04, 2026 @11:56AM (#50368367)
Gotcha, that's what I figured but I was still curious. I've got a side-project that was originally designed for traditional GitOps but got OCI support as a feature submission from a user. I've been seeing more usage of the OCI backend these days and originally figured it was a side-effect of the project domain (Podman Quadlets) but maybe it is an over all field shift.
Re:Incident with Pull Requests, Git Operations and Issues by bdsa on Wednesday November 04, 2026 @12:21PM (#50368668)
In the last couple of weeks, I've been moving a deployment stack off ArgoCD pointing at Git, and ended up settling on Flux fetching OCI artifacts from ECR. The artifacts are built and pushed by GitHub Actions. It seems like a nice way to "have GitOps" without needing GitHub to be up all the time.
Re:Incident with Pull Requests, Git Operations and Issues by c0rruptbytes on Thursday November 05, 2026 @01:39AM (#50375927)
I think so, Argo CD appsets are even getting an OCI generator in the next release (3.6)
Re:Incident with Pull Requests, Git Operations and Issues by arccy on Wednesday November 04, 2026 @10:31AM (#50367011)
This is why you ignore everything for at least 30 min before starting to investigate...
Re:Incident with Pull Requests, Git Operations and Issues by jeroenhd on Wednesday November 04, 2026 @10:33AM (#50367045)
Github is fast in updating their status compared to other companies. Amazon has to be bombed, on fire, and in the news before their status page shows anything about any ongoing issues.

I assume these companies have some kind of uptime guarantee in their contracts, because they seems to care more about covering their asses than about informing customers.

Re:Incident with Pull Requests, Git Operations and Issues by giwook on Wednesday November 04, 2026 @12:04PM (#50368474)
Comparing one shitty set of standards to another shitty set of standards… hmm
Re:Incident with Pull Requests, Git Operations and Issues by sleepybrett on Wednesday November 04, 2026 @12:53PM (#50369130)
No they aren't, we can see outages coming 20+ minutes before GH reports them.

We have outages on our books that they never reported even after we ticketed them.

They cook the stats like an inner city police department.

Re:Incident with Pull Requests, Git Operations and Issues by chanux on Wednesday November 04, 2026 @01:25PM (#50369538)
Not fraud from a legal point of view I guess /s
Re:Incident with Pull Requests, Git Operations and Issues by beardedetim on Wednesday November 04, 2026 @05:39PM (#50372482)
Me and a colleague were just ranting about how there's no way in hell Actions has 99.6% uptime but yet that's what their status page says. Maybe it's just bias and I am only remembering the minutes that it's down what feels like every week or multiple times a week. But I'm suspicious of their stats, even if they declare an incident on the status page.
Re:Incident with Pull Requests, Git Operations and Issues by sleepybrett on Thursday November 05, 2026 @01:11PM (#50382316)
I would suggest every enterprise customer that is not keeping track of github downtime and it's effect on their systems and workforce independently for presentation to their sales team every billing cycle for discounts is leaving a lot of money on the table.
Re:Incident with Pull Requests, Git Operations and Issues by deathanatos on Wednesday November 04, 2026 @06:23PM (#50372847)
> Github is fast in updating their status

Github's status page is incredibly slow in comparison to the status page Github themselves used to have, which had several key metrics of various systems that would update in real time, and when they did have a (comparatively rare) outage, would usually have at least one metric going "yeah, something is wrong".

Re:Incident with Pull Requests, Git Operations and Issues by ozyschmozy on Wednesday November 04, 2026 @01:11PM (#50369352)
> "this must be GitHub," but the status page rejects the notion, and so you go digging

Don't know about you but at this point I've learned to recognize and ignore GitHub issues even when they haven't admitted to it yet

Re:Incident with Pull Requests, Git Operations and Issues by defraudbah on Wednesday November 04, 2026 @04:07PM (#50371532)
show me one status page that's reliable, it turned into smoke and mirrors
Re:Incident with Pull Requests, Git Operations and Issues by solyin on Wednesday November 04, 2026 @04:16PM (#50371646)
downforeveryoneorjustme.com is a high level way to gather that data
Re:Incident with Pull Requests, Git Operations and Issues by thwarted on Wednesday November 04, 2026 @05:43PM (#50372518)
Extremely high level, and mainly merely "is the site accessible". However, github having issues with "issues" or "pull requests" is a functionality, not an accessibility, degradation, which can often only be discovered by actually trying to perform the action/use the functionality and comparing the result to he expected result.
Re:Incident with Pull Requests, Git Operations and Issues by spartanatreyu on Wednesday November 04, 2026 @06:20PM (#50372812)
What you're looking for:

Question 1: Is it github, or is it everyone:

Answer: https://downdetector.com/

(If everyone's having issues, then stop. Otherwise, continue below...)

---

Question 2: Is it github?

Answer 2: https://www.githubstatus.com/

Question 3: Why are you lying to me, is it github or not?

Answer 3: https://mrshu.github.io/github-statuses/

(If github is not having issues, then check your local environment. Otherwise, continue...)

---

Question 4: Why is it always github, surely they're not that bad right?

Answer: https://www.dayswithoutgithubincident.com/

(Perhaps its time to consider an alternative to github, or at least a mirror)

Re:Incident with Pull Requests, Git Operations and Issues by chrisjj on Wednesday November 04, 2026 @07:00PM (#50373134)
[delayed]
Re:Incident with Pull Requests, Git Operations and Issues by renehsz on Wednesday November 04, 2026 @10:26AM (#50366940)
https://GiveUpGithub.org - why and how to ditch GitHub.
Re:Incident with Pull Requests, Git Operations and Issues by znpy on Wednesday November 04, 2026 @11:22AM (#50367844)
I miss working with a self-hosted gitlab instance.
Re:Incident with Pull Requests, Git Operations and Issues by el_psy_congroo on Wednesday November 04, 2026 @11:29AM (#50367967)
actions still don't work correctly
Re:Incident with Pull Requests, Git Operations and Issues by esafak on Wednesday November 04, 2026 @11:36AM (#50368089)
There is a second incident: https://www.githubstatus.com/incidents/xr3myzj7ms51

Get your act together, Microsoft.

Re:Incident with Pull Requests, Git Operations and Issues by sigmonsays on Wednesday November 04, 2026 @11:41AM (#50368151)
Github only has issues on days that end in Y!
Re:Incident with Pull Requests, Git Operations and Issues by giwook on Wednesday November 04, 2026 @12:03PM (#50368465)
It’s kinda funny that GitHub having issues continues to make HN front page.

Perhaps these types of posts should just be pinned at this point.

Re:Incident with Pull Requests, Git Operations and Issues by gowthamgts12 on Wednesday November 04, 2026 @12:46PM (#50369014)
they marked incident with Pull requests, Git operations and issues - but i don't see any outage in the bars for today other than pull requests? what's the point of showing uptime there then? https://mrshu.github.io/github-statuses is more reliable than the official github status page.

new incident with actions now - https://www.githubstatus.com/incidents/h02n9572mx9y.

Re:Incident with Pull Requests, Git Operations and Issues by luciandan on Thursday November 05, 2026 @11:47AM (#50381352)
Each time something like this happens, I take another look at Forgejo. Using an AI assistant it's not that complicated to set up, but it does feel too complex. So then I accept the fact that GitHub is still the best in class for now.

Until next time. When I look into alternatives again. Probably, one day, I'll actually migrate away. But for now I shrug and tell myself that these things happen.