Generate changelogs and release notes from a project's commit messages and metadata
See original GitHub issueNew Feature Proposal
Description
Generate changelogs and release notes from a project’s commit messages and metadata https://github.com/conventional-changelog/conventional-changelog
Background
I always forget changing CHANGELOG.md
file and I believe I’m not alone in it. It would be great to update this file automatically based on git history (commit messages) once a new release supposed to be delivered.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Conventional Changelog - GitHub
Generate changelogs and release notes from a project's commit messages and metadata.
Read more >How To Automatically Generate A Helpful Changelog From ...
Creating a changelog is a usual task if a new software version is going to be released. It contains all the changes which...
Read more >Generate Changelogs & Release Notes From A Project's ...
Conventional-changelog: Generate changelogs & release notes from a project's commit messages & metadata. Generate a CHANGELOG from git metadata.
Read more >Tooling for Conventional Commits
php-conventional-changelog: a tool built to generate a changelog from a project's committing history messages and metadata and automate versioning with Semver, ...
Read more >How to automate your releases, versioning & release notes ...
What if every pull request or commit you made to your release branch would automatically generate you a changelog, figure out the required...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think we definitely could and should improve our commit messages, as we(at least I) usually don’t put much thought in them. commitlint could be good starting point. I still see value in having separate changelog, as not every commit message needs to be added as changelog entry, but if we start creating good commit messages, then maybe we can revisit this
By the way, just compare these changelog files: