3 ms·
Automated changelog generation tools usually have a mechanism to allow you to opt commits in or out of the changelog. So you still get authorial control over t
by madeofpalk 2y ago
Automated changelog generation tools usually have a mechanism to allow you to opt commits in or out of the changelog.
So you still get authorial control over the changelog, but when it comes to actually creating the document it’s automated because you wrote the individual lines when you wrote the code.
It’s basically the same as what you’re doing, but in a different order.
- remram 2y agoThat works if commits can be looked at in isolation to build the changelog. What if a commit introduces a feature, and a subsequent one changes it? Is there a syntax for your commit to replace an earlier changelog entry? Cue the Kubernetes release notes, which contain 20 separate "update to Go x.y.z" for each release.
- madeofpalk 2y agoThe way I've always done it is that it's controlled via labels on PRs. If you want to remove a PR (and by swashing merges). If you want to remove a PR from the changelog, remove the label.