git dibs

We’ve all had it happen to us. You wake up, roll over to grab your phone, and check your company’s commit log. And then you see it. Someone else has taken the commit id you wanted. And you’re crestfallen. Photo by Claudia Wolff on Unsplash Maybe it was an elegant one like 184bdd8e5dd39de66d48cd8b5e48d64c1a78d7ef or a more prosaic one like 8834fc4b992220d3eb2679557eccb6654453bfb1, but the result is the same. For me personally, I went as far as pinging all 300 developers on our Slack instance that I wanted adf3e0e8c5ffdc913ccf62cd3b349a1ece09f578, and a couple days later someone took it anyway. And when I asked them why, why would they do something so petty and cruel, all they could say was “What is actually wrong with you?” I reported them to my mom but nothing’s happened yet. Today I’m introducing git dibs so nobody ever takes your coveted commit hash again. With git dibs you can call dibs on a 40 hexadecimal-character SHA-1 hash, asserting your right to use it to identify a future…