There’s a community standard out there called Conventional Commit for structured git-commit messages. If you don’t know about it already, it recommends a strict type(scope?): description format for describing a code change in a repo.
I agree with your argument. My main use case of tags is to indicate if that commit builds or not, I could probably just reduce it to a Boolean represented by one character, that way I’d get differentiation in my synopsis while still compressing it.
This thread has given me a lot to think about. I may abandon my current form of tagging. Idk tho, it’s nice to be able to visually filter chore commits from features from wip from fixes.
I agree with your argument. My main use case of tags is to indicate if that commit builds or not, I could probably just reduce it to a Boolean represented by one character, that way I’d get differentiation in my synopsis while still compressing it.
This thread has given me a lot to think about. I may abandon my current form of tagging. Idk tho, it’s nice to be able to visually filter chore commits from features from wip from fixes.
I’m torn.