A changelog generator turns the commits or pull request titles of a release into notes your users can read: grouped into new, improved and fixed, with the internal noise left out. Free, no signup, and it runs in your browser.
Tip: git log --oneline v2.3.0..HEAD and paste the output. Nothing leaves your browser.
12 lines → 8 user-facing changes · 3 internal hidden · 1 merge skipped
Now tell the people who asked for it.
Post this changelog in Melonhelp Feedback and everyone who requested or voted for a change gets an email. Free plan, no card.
Paste whatever your history looks like. Hashes, bullets, list numbers and(HEAD -> main)decorations are stripped, and duplicate lines are merged.
Everything since your last tag
git log --oneline --no-merges v2.3.0..HEADThe last two weeks
git log --oneline --no-merges --since="2 weeks ago"Merged pull requests (GitHub CLI)
gh pr list --state merged --limit 50 --json number,title --jq '.[] | "\(.title) (#\(.number))"'Conventional Commits prefixes win. Lines without one are sorted by their first verb, and anything that matches nothing lands in Improved. To move a line, add a prefix like fix: in the box.
A dated list of the changes in each version of a product, written for the people who use it. A good one groups changes into new features, improvements and fixes, and leaves out internal work like refactors, CI tweaks and dependency bumps.
Mostly scope. A changelog is the running history of every version, usually one page you keep adding to. Release notes cover a single release and often add context, screenshots or upgrade steps. The output of this tool works as either: paste one release's commits and you get that release's notes, ready to add on top of your changelog.
No. It runs entirely in your browser with fixed rules, no AI and no server calls, so private repository history never leaves the page.
Yes. feat goes to New, fix to Fixed, perf to Improved, and a type with ! or a BREAKING CHANGE note goes to Breaking changes. chore, ci, test, docs, build, style and refactor are treated as internal and hidden unless you turn them on. Scopes like feat(billing) become a bold label. Commits without a prefix are sorted by their first verb: add, fix, remove, improve and so on.
Run gh pr list --state merged --limit 50 --json number,title --jq '.[] | "\(.title) (#\(.number))"' with the GitHub CLI, paste the output, and add your repo as owner/repo so every #number links to its pull request.
It follows the same idea: newest version first, a date on every release and changes grouped by type. Keep a Changelog names its groups Added, Changed, Deprecated, Removed, Fixed and Security; this tool uses New, Improved, Fixed and Removed, plus Breaking changes, which read better for end users. Rename the headings if you need the exact spec.