[yooogle]

First of all, the linked gist doesn't provide any new information. It states "See how a minor change to your commit message style can make you a better programmer." then proceeds to say nothing on that topic.

Putting all that aside. I've used the conventional commit format in many of my projects. So far, I've found that without a tool to handle the format for me, I am simply too lazy to sustain that format for more than a few days.

Also, there become situations where your commits contain new code for multiple features that are all related. Or, there are times when I am simply committing code before completing a feature just in case I want to roll something back.

In these cases, there often isn't a good "type" that optimally covers the full scope of what is occurring.

It seems that many of the things we do as programmers are just superfluous ways of "making things easier" or "more organized" that ultimately just waste time and result in unfinished projects.

[jasonpeacock]

> I've found that without a tool to handle the format for me, I am simply too lazy to sustain that format for more than a few days.

That tool is Git, it's already built-in. You can create a Git commit template, with the correct format, and then in the comments of the template you list out the semantic options for quick reference.

See `commit.template` here: https://git-scm.com/book/en/v2/Customizing-Git-Git-Configura...