gitmoji VS gitmoji-cli

My commit messages are pretty good though. I put some effort/thought into them not just for the repo/git purposes, but it also helps me mentally keep track of what I have done / have to do just in the general carry-on coding. I even prefix messages with an emoji, similar to the guidelines on https://gitmoji.dev/

You may also turn on GitMoji convention if you prefer your messages baked with emojis 🤠

I use Gitmoji:

https://github.com/carloscuesta/gitmoji

OpenCommit leverages the conventional commits convention, ensuring your commit messages are both concise and informative. Want a little fun in your commits? Enable the GitMoji setting!

The library uses conventional commits convention which makes commits concise and comprehensive. You can also turn on GitMoji setting if you like.

At a previous job we used https://gitmoji.dev, which scrumoji is based on. At some point I started using the ladybug emoji for bugs because it's actually a bug while my colleagues kept using the caterpillar emoji because they preferred caterpillars. I thought it was a nice way to bring some individuality into our commit messages!

It's the first time I see someone combining gitmoji with conventional commits (I use the later now for all my project, to generate my changelogs automatically with with git-cliff.)

It still happens today: https://github.com/carloscuesta/gitmoji

While there is gitmoji-cli, there are times when I just want to use another emoji that has not been incorporated into the gitmoji project. For example, I may use a cookie (🍪) when writing a commit message related to work on HTTP cookies, or a vomiting face (🤮) for a commit which adds a lot of debug statements.