git-cliff VS cacao

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

This is really specific, but for this point in the article:

> There’s a long guide on Embedding a Command-Line Tool in a Sandboxed App, so I followed that, and then slowly, painfully, factored Xcode out of it, so that I wouldn’t have to figure out how to get a 10GB Xcode install onto the CI machine (remember, you need to be signed in to an Apple ID to download Xcode, and there’s no way to do it from the command-line).

You could actually solve this with Rust and no Xcode whatsoever. cacao [1] and cargo-bundle [2] will produce an app bundle you could sign/notarize/distribute without needing to ever open Xcode.

[1] https://github.com/ryanmcgrath/cacao

I've had basic animation support in cacao for about a year now, but I don't think anybody even realizes it.

But I will reiterate what I say on many posts like these, which is that it would be even cooler if we could stop having a million projects reinvent this wheel - and I say this as someone who wrote a large Rust library that is backed by ObjC. madsmtm has an ongoing effort to put together a best in class ObjC Rust wrapper, which would be great to see even more support for.

MacOS; I have to call the AppKit API. I can use a library like this which offers Rust bindings for AppKit - otherwise I can write my own maybe?

Yes, you can: https://github.com/ryanmcgrath/cacao