31 ms·
As far as I can tell, the autogeneration of changelogs you can do with standard-version https://github.com/conventional-changelog/standard-version https://githu
by tmcw 8y ago
As far as I can tell, the autogeneration of changelogs you can do with standard-version https://github.com/conventional-changelog/standard-version https://github.com/conventional-changelog/standard-version and commitzen ( https://github.com/commitizen/cz-cli https://github.com/commitizen/cz-cli ) fulfills the criteria Keep a Changelog wants: right date format, clear notes for breaking changes, and no unnecessary information from irrelevant commits. I've really liked using the two for a variety of systems - the strict commit message formatting and opinionated changelog generation means that the resulting changelogs are pretty darn readable. But ymmv.
- _asummers 8y agoSeconding this recommendation. Recently began using them at work and it's improved engineering <--> company communication, as well as engineering <--> engineering communication since I can look at the generated changelog and know exactly what changed there, in ALL commits.
- toyg 8y agoThese are node-specific tools. Do you know of anything similar but generic? Ideally, one would have something that can be connected to project-management tools rather than github, e.g. Trello: when you mark a checklist or archive a card, the title should go in changelog.
- StavrosK 8y agoI would like something generic as well. I used to use semantic-release[1] but it's a bit too Github-specific for my tastes. [1]: https://github.com/relekang/python-semantic-release https://github.com/relekang/python-semantic-release