Turn conventional commits into a changelog entry in Keep a Changelog or conventional-changelog headings, with unparsed commits listed rather than dropped.
Waiting for commit messages
`git log --format=%B v1.1.0..HEAD` gives you exactly the right shape.
Paste some commits to build a changelog entry.
Keep a Changelog's headings and the conventional commit types are two different vocabularies, and mapping one onto the other is a judgement. `refactor` has no Keep a Changelog heading because a reader does not care about one; `perf` goes under Changed rather than getting a section. A changelog is written for people, so read it before publishing it — this gets you the structure and the entries, not the editing.
Changelog Generator runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
A changelog is written for people and a commit history is written for machines, which is why generating one from the other is a translation rather than a transcription. This does the mechanical part — grouping, ordering, formatting — and leaves the editing to you, because that is the part that makes a changelog worth reading.
Keep a Changelog's six headings and the conventional commit types are two different vocabularies, and the mapping between them is a judgement. `refactor` is a real commit type with no Keep a Changelog heading at all, because a reader does not care that the internals moved. `perf` lands under Changed rather than getting a section of its own. Both heading sets are offered and the mapping is stated rather than assumed.
Commits that do not parse as conventional are listed separately instead of being dropped. A changelog quietly missing three entries is worse than one with a visible gap, because you find out about the gap from a user.
The implied release is computed alongside, from the same commits, so the version at the top of the entry and the contents underneath it agree.
Everything happens in the page. Commit bodies often mention internal systems, customers or security issues, and none of that is uploaded.
A convention for writing changelogs by hand, with six fixed headings — Added, Changed, Deprecated, Removed, Fixed, Security — chosen for what a reader needs to know. It predates conventional commits and is aimed at a different audience, which is why the mapping between them takes judgement.
Either they did not parse as conventional commits, in which case they are listed separately below, or their type has no changelog section — `chore`, `test`, `style` and `refactor` are left out by default because they tell a user nothing. The switch includes them if you want them.
No. A changelog is a summary of what changed for the people using the software. A full list of commits already exists in the git history and serves a different purpose.
This produces one version's entry, which is what you add at the top of an existing CHANGELOG.md. Generating the whole file from the whole history usually produces something nobody wants to read.
No. The commits are parsed in your browser, which matters because commit bodies routinely mention things that should not leave your network.