Paste your merged changes
One per line — conventional commit prefixes (feat/fix/chore) are recognized automatically.
AUDIENCE-READY RELEASE NOTES
Convert a list of merged changes into organized release notes grouped by type, written for your intended audience.
Planning guidance only. Validate important decisions with customer evidence and your delivery team.
YOUR INPUTS
Complete every field. The result updates only when you choose Calculate.
One per line — conventional commit prefixes (feat/fix/chore) are recognized automatically.
End users, developers, or internal team each get different section labels and framing.
Changes are grouped by type into ready-to-edit sections.
Continue learning: Writing release notes users actually read
Ungrouped changes land in an 'Other' section — you can still edit and re-categorize them manually, and consider adopting prefixes going forward for automatic grouping.
No — it groups and labels changes, but you should still edit technical wording into plain language before publishing to a non-technical audience.
Yes — the 'Internal team' audience option uses more direct, less polished labels suited for internal tracking rather than public announcements.
It's the percentage of pasted changes that were successfully recognized by a conventional commit prefix (feat/fix/chore) versus left as 'Other.'
| Feature | MVPHub | GitHub Releases | Notion |
|---|---|---|---|
| Instant audience-specific grouping | Included | Not included | Not included |
| No account or repo access required | Included | Not included | Included |
| Conventional commit recognition | Included | Limited | Not included |
| Auto-generates from actual commit history | Not included | Included | Not included |
GitHub Releases can auto-generate notes from commit history when connected to a repo. This tool works from a pasted list, independent of any repo connection, and tailors the output to a specific audience.
Add this tool to your site with the canonical iframe below. It remains hosted and maintained by MVPHub.