Closed carmenbianca closed 1 month ago
I like the approach, quite simple. An alternative approach I see in projects is to generate a changelog as part of creating a release. This can be automated using tools. If we want to keep creating changelog entries as part of the pull-requests I think the approach supported by Protokolo is a nice one.
I don't like generating change logs from VCS history. Hand-curated change logs are so so so much better, even if they're a touch more work.
I wrote Protokolo.
It solves problems for me. Copying from its README:
Let's use it after the next release.
Some things that are needed:
protokolo init
(and manually editingCHANGELOG.md
to include<!-- protokolo-section-tag -->
)CONTRIBUTING.md