Accidentally breaking GitHub Actions with a shorthash collision (2019)
blog.teddykatz.com
blog.teddykatz.com
* Automated use? Always use full hashes
* Human use? Short hashes are usually fine, but a full hash doesn't hurt (and please make it available in a link/hovertext)
> You want to look at [a123456](some.git.url/a12345678...) to see where we've done this before
I can't promise that the repo won't have changed by the time they look at it (but because the full hash is linked, it's not a problem in practice).
It does what?!?!
So if i have a repo which does not contain commit abcdef, and some random evil bastard forks it, and adds a commit abcdef, then users can ask for commit abcdef from my repository, and get the commit the evil guy added? That seems surprising and bad!
> This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
I always thought HCL was a fairly smart/interesting choice, and I’ve always wondered if they backed out because users were unfamiliar with HCL, the ecosystem wasn’t ready for HCL, or something else.
In the meantime, the article is right that you should use the full-length digests for situations where you care about reproducibility.
The writing is on the wall with their abuse of customers on Windows 11.
Microsoft gives me AOL vibes, where the ancient customers will be squeezed until the end.