Does anybody have any workflow for converting GitHub milestones + issues into a changelog? I've been digging around and it seems like there's handfuls of tools out there, but they all seem messy and overly complex. I'll probably end up writing my own tooling, won't I?
@gabek I use squash-on-merge for PRs so there is only a single commit in main per PR, and word my PR titles according to https://keepachangelog.com/en/1.0.0/ Then, I get the git log between the last release and HEAD, and sort the commits into categories of the changelog. I also make sure to remove entries that have no meaning to the end-user, such as refactors, tests, or dependency updates.
@Gargron That makes a lot of sense, and sounds like exactly what I'd want to do. That web site is a nice guide, I hadn't seen that, thanks for sharing!
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!