Changelog generator from git commits

Paste your commit messages and get a Keep a Changelog entry. Free, no sign-in, and it runs in your browser.

One commit per line. Paste the output of git log --oneline or a list of pull request titles.

Keep a Changelog entry
## [1.2.0]

### Added
- Add pdf export (#142)
- **ui:** Export button in the toolbar

### Changed
- Open large reports faster

### Fixed
- Oauth redirect loop (#139)
- Typo in settings

5 included, 3 skipped as noise

This tool runs in your browser. What you paste is not sent anywhere.

Want notes your users can read too?

This tool sorts commits by type. ReleaseTale reads the commits and pull requests of a release and writes plain-language release notes for your users as well as the developer entry.

Start free

How commit types become changelog headings

The tool reads each line as a Conventional Commit and places it under one of the six headings of the Keep a Changelog format.

Commit typeHeadingMeaning
featAddedA new feature
fixFixedA bug fix
perf, revertChangedA change to existing behaviour
feat!, fix!ChangedA breaking change, shown first and labelled
deprecateDeprecatedSomething that will be removed
removeRemovedSomething that was removed
securitySecurityA vulnerability fix
chore, ci, build, test, docs, style, refactor(left out)Work that readers do not notice

From a draft to a changelog people read

A sorted list of commits is a starting point. Before you publish it, read each line as a customer would, merge the lines that describe one change, and move breaking changes to the top. The guide on how to write a changelog lists the habits, and the Keep a Changelog template gives you the file around the entry. To see the same release written for users and for developers, look at the changelog examples.

Already have a changelog? Check it with the CHANGELOG.md validator. Not sure which version to give the release? Try the version bump calculator.

If you release often, the GitHub release notes automation setup shows how to get a draft on every tag.

Frequently asked questions

How do I generate a changelog from git commits?

Run git log --oneline between two tags, paste the lines into the tool and choose a version. It groups Conventional Commits by type into the Keep a Changelog headings and leaves out chores, tests, docs and merge commits.

Is my commit history sent to a server?

No. The tool runs in your browser, so what you paste never leaves your machine.

What if my commits do not follow Conventional Commits?

Keep the option for other lines switched on and they are listed under Changed. You will want to reword them, because commit messages are written for maintainers rather than for readers.

Is the result ready to publish?

It is a first draft. Read it, merge related lines, rewrite jargon and call out breaking changes before you publish. A tool can sort commits, but a person decides what matters to the reader.