4 ms·
use https://www.conventionalcommits.org/en/v1.0.0/ https://www.conventionalcommits.org/en/v1.0.0/, it has extensions that can autogenerate a nice looking change
by sss111 4y ago
use https://www.conventionalcommits.org/en/v1.0.0/ https://www.conventionalcommits.org/en/v1.0.0/, it has extensions that can autogenerate a nice looking changelog.
- jasonpeacock 4y agoYep, something like Git Cliff[1] is great for generating release notes from your commit messages. And conventional commits are good thing to do regardless of whether you use them for release notes or not. Commit messages should be helpful and immediately obvious, too often its "fixed bug" or "finally figured out foo!", which really tell you nothing - might as well not have a message. [1] https://github.com/orhun/git-cliff https://github.com/orhun/git-cliff
- difosfor 4y agoYeah, at work we combine that with https://semantic-release.gitbook.io/semantic-release/ https://semantic-release.gitbook.io/semantic-release/ for changelog generation and continuous deployment to NPM. It takes some getting used to, but I like it.
- agateau 4y agoThis is the kind of tools I dislike. It does generate a "nice looking changelog", but the result is not as useful as a separately written changelog, because the content is not curated, so the signal-noise ratio can be quite high.