git-cliff VS gitmoji

git-cliff is a terminal tool that can generate changelog from the Git history by using conventional commits, as well as by using regex-powered parsers and you can even change the changelog template itself by using a configuration file. This tool is a great example of text parsing on the terminal and also uses clap_mangen which generates man pages. Useful for anyone who is serious about looking into making a production-ready terminal tool!

Solutions exist for this. Our company does this with git-cliff. Using conventional commits, any commit labeled with the subject "www" will appear in our public changelog.

This was primarily aimed to work with git-cliff to generate changelogs for GitHub releases, since tagging contributors would include them as contributors for the release, while also ensuring structured changelogs thanks to git-cliff. As of now, it requires a few extra steps to get it working with git-cliff, but the integration should be much better once the PR for post-processors is merged.

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.)

Gitmoji ✨ add integration with xpto

Do not forget to use emojis in your commit messages. 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

If you are a fan of gitmoji (I am not - but its something some people seem to like) https://gitmoji.dev

The lib uses conventional commits convention which makes commits meaningful. You can also turn on GitMoji setting if you like. And select different languages and many other features (I got 12 PRs so far)

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!