I'm not sure that I like the fact that gut pushes the emoji thing onto users. IMO a good commit message will be descriptive enough that you really don't need an explanatory emoji. For example, if I have a commit titled "Add documentation for SomeAPIClass", I really don't need a book emoji in front of that, because I made it clear that it was documentation.

If you are going to add emoji to a git commit, make sure it's appropriate. For example, if you add a feature to your app that shows confetti, you might add a party popper emoji to the commit message, but you shouldn't litter your git history with emoji unnecessarily.

I guess I could continue ranting about the people who add "feat:", "chore:", and the like to their commit messages, but what I've written about emojis here really applies to the plaintext tags as well.

I am just impressed that the author was able to consistently think of relevant emojis for 100+ commit messages.

Actually, I never did. I use Gitmoji:

https://github.com/carloscuesta/gitmoji