Incident with Pull Requests, Git Operations and Issues

thesdev

Finally a GitHub outage during European workday. Yaaay.

esher

Again and again?

chinathrow

git clone works sometimes, sometimes not.

sognetic

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

igleria

Can't they just... sell github back like when the germans sold the nuclear plant back to mr burns?

eknkc

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.

fauzanhilmi

For a moment I thought my ssh key got breached. Fricking hell Github!

dude250711

These days, perhaps, normal undisrupted operation should start counting as an incident...

cashbreaker

I was thinking I'm going crazy with me ssh keys not working on both of my machines.

larsnystrom

Why haven’t they asked an AI agent to fix all their bugs yet? /s

feukon

The day GitHub will no longer be free is approaching... they just can't support the abnormal amount of things being pushed rn

rarisma

- - > i wake up - - | | | V github has an outage

grishka

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 "permission 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.

misnome

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.

rvz

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

marvstazar

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-...

malikolivier

GitHub outages can be a drain on productivity. 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...

a-squirrel-comm

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.

fredsted

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.

swe_dima

Temporary workaround is to do git config --global url." https://github.com/".insteadOf git@github.com: so it pushes / pulls using HTTPS when things are back to normal run: git config --global --unset url." https://github.com/".insteadOf