Turn your git log into a changelog.
Paste your git log — either --oneline or the
default format — and get a clean Markdown changelog. Commits
are grouped by Conventional Commit type (Features, Bug Fixes,
and so on), breaking changes are surfaced at the top, merge commits are
dropped, and hashes are optional. It all runs in your browser —
nothing is uploaded.
FAQ
Is my data uploaded?+
No. Your git log is parsed and converted entirely in your browser — it is never sent to a server. We count only anonymous, aggregate usage on our own server (a page view, that a conversion ran) — never your commits, hashes, or messages.
Which git log formats are supported?+
Both common ones. Paste git log --oneline (<hash> <subject> per line) or the default git log output with its commit / Author: / Date: blocks. The tool detects which you pasted and reads the subject of each commit.
How are commits grouped?+
By Conventional Commit type. feat goes to Features, fix to Bug Fixes, plus sections for perf, refactor, docs, test, build, ci, style and chore. Anything that isn't a recognised type lands in Other, and a scope like feat(api): is rendered in bold.
What counts as a breaking change?+
A ! after the type or scope (for example feat!: or feat(api)!:), or a commit body containing BREAKING CHANGE. Those entries are also collected into a ⚠ Breaking Changes section at the top so they are impossible to miss.
Are merge commits included?+
No. Subjects that start with Merge are skipped, so the changelog stays focused on the actual work. Turn off Include commit hashes if you want the cleanest possible release notes without the trailing (`hash`).