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.
Yeah these are just awful to read. Feat/bug/chore is pretty much the most useless information to know about a commit.
You should just describe the change. On very large projects having a component: prefix can be useful but honestly, barely. The most common way to arrive at a commit is through a link or git blame or similar when you already have context. I very rarely actually exhaustively read a list of commits.
And if you want to automate your change log (which you probably shouldn’t do anyway), you can just as easily put that metadata in the commit body. In fact it’s probably better there because you can write a user-targeted description too.
Conventional Commits is one of those weird ideas that seems to make developers think they’re doing something useful but only if you don’t think about it too much.
Yeah these are just awful to read. Feat/bug/chore is pretty much the most useless information to know about a commit.
You should just describe the change. On very large projects having a
component:prefix can be useful but honestly, barely. The most common way to arrive at a commit is through a link or git blame or similar when you already have context. I very rarely actually exhaustively read a list of commits.And if you want to automate your change log (which you probably shouldn’t do anyway), you can just as easily put that metadata in the commit body. In fact it’s probably better there because you can write a user-targeted description too.
Conventional Commits is one of those weird ideas that seems to make developers think they’re doing something useful but only if you don’t think about it too much.