Feoh on Nostr: npub172v3n…u689n Release -> Devops engineer here :) I think there is! Though I'll ...
npub172v3nlrtzd8wssn8f3ckm47jtsxdhq0jakqua3crgrvn7mmv32vsju689n (npub172v…689n) Release -> Devops engineer here :) I think there is! Though I'll leave it up to you to judge whether or not it's Good Enouigh for you to adopt.
The v for tags convention solves the problem of, as a human, not being able to readily discern the nature of a Git entity I'm being asked to check out.
I can hear you asking "Why does it matter? Isn't everything just a pointer to a commit at the end of the day?"
Not really IMO.
If I'm checking out a branch, the implication is that checkout is mutable, whereas if I'm checking out a tagged commit, that's fixed in time unless the tag changes, and generally you don't want that.
lmk if any of this makes any sense to you or if I can help in any other way.
The v for tags convention solves the problem of, as a human, not being able to readily discern the nature of a Git entity I'm being asked to check out.
I can hear you asking "Why does it matter? Isn't everything just a pointer to a commit at the end of the day?"
Not really IMO.
If I'm checking out a branch, the implication is that checkout is mutable, whereas if I'm checking out a tagged commit, that's fixed in time unless the tag changes, and generally you don't want that.
lmk if any of this makes any sense to you or if I can help in any other way.