91
Git 3.0's upcoming SHA-256 default will be a costly mistake
(blog.gitbutler.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Oct 2026
91 points (92.5% liked)
Programming
29221 readers
447 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
thats bad, i got couple of repos on sha-256, i wonder what happens if they drop it, which i think they wont, do i have to like re-create them?
I don't think they'll drop sha256. The breaking change is that it's now the default instead of sha1.
It's too late for this to have any effect. It's more "brace for the shitty unnecessary storm".
If you thought "main" was stupid...