4 ms·
I use the git log to feed my changelog. I prefix the stuff that's supposed to go in the release notes with a asterix and the technical boring stuff is just a no
by mulle_nat 4y ago
I use the git log to feed my changelog. I prefix the stuff that's supposed to go in the release notes with a asterix and the technical boring stuff is just a normal line. Then at release time I have a script that pulls the asterix prefixed lines from the change log into the RELEASENOTES.md. I wouldn't want to bother with more.
- kreeben 4y agoHow do you know that your asterixed commit should go into the release notes? What if... * fixed thing X so that user can do Y broke things so that another commit is needed: * fixed X again, so that user can finally do Y (for realz this time) This would not make a great release note.
- ehPReth 4y agoyou just wouldn't put a * in front of the second one
- justinfrankel 4y agoor you might have an alternate prefix for "things that go in development build changelogs but not final changelogs", e.g. "-"
- slavik81 4y agoWhen you squash and merge a PR, GitHub will by default prefix commit messages of the squashed commits with an astrix.