157
Github confirms random 401 responses on unauthenticated git clones are no mistake (eviltoast.org)
submitted 6 days ago by orhtej2@eviltoast.org to c/programming@programming.dev
76 comments fedilink hide all child comments

Since yesterday a lot of users in Europe found their workflows failing due to Github seemingly randomly throwing HTTP/401 on git clone/git pull when interacting with public repos without authentication.

It was now confirmed by staff member that this indeed is intentional and no further steps are planned at this point.

you are viewing a single comment's thread
view the rest of the comments
[-] eager_eagle@lemmy.world 0 points 6 days ago* (last edited 5 days ago)

That doesn't affect me, but you can't eat your cake and have it too. I'd rather have open source content actually open and easy to access, but GitHub has an availability issue and they're trying to address it, so I don't see this as a hostile move.

I'm sure if codeberg was nearly as popular as github, they'd be forced to restrict some clones too. Their current load is unprecedented, even for their standards.

this post was submitted on 03 Sep 2026
157 points (99.4% liked)

Programming

28405 readers
495 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev