gitmoji VS semantic-release-gitmoji

Gitmoji uses emojis to indicate the type of change.

I won't recommend it specifically, but I recommend to have a standard. I prefer a standard that I don't like rather than a not having a standard. Other options that I remember:

- The kernel patch descriptions: https://kernelnewbies.org/PatchPhilosophy. Used by the repository that Git was created for (the Linux kernel) and Git itself;

- Gitmoji: https://gitmoji.dev/, similar to conventional commits but using emoji

Personally we may like them or not. But again, even though I don't like it, I would a history with ": do foo in bar" instead of a history with a lot of commits only named "fix", "now it works" and things like that.

Based on the usage described above, Gitmoji has the same unbuild setup, the below is the Gitmoji package.json

This prompt defines the format of commit messages according to Conventional Commits with the addition of emoji (gitmoji). It consists of the following elements:

This GH CLI extension implements the Angular convention for commit types, combined with gitmojis. It does not support scopes, or message bodies. For feedback, suggestions and bug reports, please open an issue.

Sidenote: If you're more the picture-type, you could think about using gitmoji as types.

I'm not sure how new the trend is, but it's called gitmoji (https://gitmoji.dev/) and there's also tooling to make committing/searching for the "correct" emoji easier :D Whatever makes your job more fun, right? Oh and it saves on characters!

I use this in all my projects, and even use: https://github.com/momocow/semantic-release-gitmoji plugin with https://github.com/semantic-release/semantic-release to automatically increment versions. I run it in GitHub actions