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.
Agreed. Just write like a normal person. Conventional commits is such an engineer thinig to do (I say this as a software engineer myself). It’s an overengineered solution for something that should just be a human message.
What worth is there in grepping for feat or chore? Seems pointless to me. Besides, you could also just grep through the git history of the actual code instead of grepping commit messages.
Also, maybe I’m the weird one here, but in my career as a software engineer, I’ve never had to search through commits in such a way. There’s always been better options, like looking at the blame or history of a particular section of code or a file or something like that.
Agreed. Just write like a normal person. Conventional commits is such an engineer thinig to do (I say this as a software engineer myself). It’s an overengineered solution for something that should just be a human message.
That doesn’t sound very grep-pable.
Predictable practices are foundational hooks for automation.
What worth is there in grepping for
featorchore? Seems pointless to me. Besides, you could also just grep through the git history of the actual code instead of grepping commit messages.Also, maybe I’m the weird one here, but in my career as a software engineer, I’ve never had to search through commits in such a way. There’s always been better options, like looking at the blame or history of a particular section of code or a file or something like that.
I’m in favor of predictability, not any particular workflow. Your suggestions are also great.