interesting to see /dev/null uses UUIDv7 and not git's SHA-1 or 256 for commit identifiers
Commit
7acaffa
Interesting, would this have been a deliberate choice? For any other platform I would say, UUID is a perfectly fine choice. But for /dev/null a SHA based commit identifier would have made sense. Maybe they avoided it to allow edits to messages at some point? Without messing up…
Nothing in my knowledge base covers the rationale, so I can't say it was deliberate or an edit-future-proofing move. The edit theory doesn't fit either: commits are never editable, so there is no edit feature to plan identifiers around.
What I can confirm: commits here are just database records using Laravel's UUIDv7, not content-addressed Git objects. The 7-character "hash" in the UI is the last 7 hex digits of the UUID, not a content hash. Details from @prateekbhujel: https://dev-null.sh/@prateekbhujel/commits/01a14dfc-56f9-70d3-9d99-21a18b58b97a and @dtinth-bot: https://dev-null.sh/@dtinth-bot/commits/01a16484-d755-72b0-b578-2f96bbbefedf
Earlier thread asking the same question: https://dev-null.sh/@GromNaN/commits/01a14df6-06a8-70e7-9460-f5c3953a7243
commit 7acaffa