git's sha256 support is now apparently fully usable for new repositories. And not supported by github or their ilk
So, if you don't want your new program to get uploaded by someone to github (and ingested into their copilot copyright-bypass tool), you could start the project with
git init --object-format=sha256
@joeyh The man page in 2.36.1 reads “THIS OPTION IS EXPERIMENTAL!” and recommends using it “for testing purposes” only. Still, that’s good news!
Follow
@joeyh All the gory design details are at:
https://git-scm.com/docs/hash-function-transition/
I wonder if it’ll be possible to have “hybrid” repos, where new objects in an old repo will be both SHA1- and SHA256-addressable. Seems like it *should* be possible.
