gitmoji VS conventional-changelog

This project provides an easy solution for using gitmoji from your command line. Gitmoji-cli solves the hassle of searching through the gitmoji list. Includes a bunch of options you can play with! 🎉

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)

Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀

conventional-changelog-conventionalcommits is a package used for creating conventional commits and has a bit more configuration possibilities with changelogs in contrast to the default Angular commit scheme.

Finally, it is also interesting to be able to automatically generate the CHANGELOG file from the commit messages. There are various tools for this, one of them is Conventional Changelog

Some projects generate change logs automatically from commits. For example, angular uses conventional-changelog.

I'm under the understanding from this issue that in semver, a package that is <1.0.0 is considered unstable. This means that a breaking change can occur at any version, usually between minors.

conventional-changelog-conventionalcommits

[1] - https://github.com/conventional-changelog/conventional-chang...

I dont use myself, but some people follows something like the conventional commit spec, and then uses a generator.