committed VS ouch

I use https://github.com/crate-ci/committed and pre-commit (the python app)

committed just reads commit messages between a range of commits, after resolving refs

For colors, I've found yansi to be great to work with. I then use concolor-control (example) and `concolor-clap (no clap3 support yet, example part 1 and example part 2). As you can see, I also like to organize my colors by the styling role they fill. The only reason I wrapped in that example is its part of the crate's API and didn't want the public API tied to yansi.

While auto-generated changelogs aren't the best, they are better than nothing. Too often I've seen projects without a changelog which is especially annoying when dealing with breaking changes.

I've been considering switching to a changelog generator, either from Conventional Commits or from a folder of files just to avoid merge conflicts with the CHANGELOG file.

If people want enforcement of Conventional Commit, check out https://github.com/crate-ci/committed

There's one that's also written in rust: https://github.com/ouch-org/ouch

I use for some time Ouch, It's a CLI tool for compressing and decompressing various formats (at this moment .tar, .zip, .gz, .xz, .lzma, .bz, .bz2, .lz4, .sz, .zst). You can compress, decompress or list archive. It's just one binary application, without dependencies and for my usage is very fast. I don't create a lot of archives, I usually unpack them when I download something from the web and so far I'm very happy with ouch. It has a simple command syntax. I use on my machines with Debian musl version from release page and on Arch there are packages in AUR (to build with cargo or binary version).

I personally use ouch. It suppirts a bunch of stuff and to quote the readme:

ouch - a command-line app to unify file compression and decompression

Shameless plug here, my favorite project currently is ouch, nobody knows about it, but I think it might gain some traction when we publish it again.