concolor VS committed

concolor-clap

I'm a little leery of clap taking on the role of color control. I've found that each library with "auto" support does it slightly differently and that really the best place for that policy is in the caller so there is a consistent experience and so it can adapt to the caller's needs. The WG-CLI has talked about this in the past and concolor family of crates is the result. I'm waiting on feedback for termcolor's use case (non-ANSI) before going 1.0 at which point we will probably make this the backend for clap's auto color support.

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