How to use the Changelog Generator
- Paste commit subjects (git log --oneline works).
- Set the version, date and optional compare link.
- Copy the CHANGELOG.md entry.
What does this tool do?
The Keep a Changelog format groups changes under Added, Changed, Deprecated, Removed, Fixed and Security, newest version first. Conventional Commit prefixes are mapped automatically, scopes are shown in bold and commit hashes are removed. Housekeeping commits like chore, ci, docs and test are left out.
Everything runs in your browser — nothing you paste is uploaded.
Why use it?
- Sorts commits automatically.
- Flags breaking changes.
- Compare links.
Use cases
- Write release notes for each version.
- Keep CHANGELOG.md up to date on open-source projects.
- Summarise a sprint for stakeholders.
From commits to a changelog
“feat(api): add search endpoint”, “fix: handle empty cart” and “chore: update deps” become:
## [1.4.0] — Added: **api:** add search endpoint. Fixed: handle empty cart. (The chore commit is left out.)
Common mistakes
- Copying raw commit messages that users won't understand.
- Leaving out breaking changes or security fixes.
- Forgetting to update the compare link for the new version.
Privacy
Everything you type is processed in your browser. Nothing you enter is sent to our servers or stored by us. There's no account to create and nothing to install.
Frequently asked questions
Where do I get the commits?
Run git log --oneline v1.3.0..HEAD and paste the output.
What if my commits aren't conventional?
Prefixes like feat: and fix: are grouped automatically; for other messages, check where they landed and edit the entry before publishing.
Why is the newest version first?
Readers usually want the latest changes, so Keep a Changelog puts them at the top.
Content last updated . See how M2Toolkit works.