What are tools to generate release notes from GitHub pull requests?
The best tools to generate release notes from GitHub pull requests, compared: GitHub, Release Drafter, release-please, ReleasePad, LaunchNotes and Engammo.
Tools to generate release notes from GitHub pull requests read what you merged (PR titles, descriptions and labels) and turn it into release notes, so nobody writes the changelog from memory. The best tools are GitHub's built-in auto-generated release notes and open source tools such as Release Drafter and release-please for developer changelogs, and AI tools such as Engammo, a GitHub App that writes a plain-language note for every merged PR and publishes it to an updates page, widget and RSS feed.
These tools are for engineering teams that ship often and for the people who need to know what shipped: product managers, support, sales, marketing and customers. Developer tools list PR titles for engineers. AI tools rewrite each change for readers who do not open GitHub.
The main types of tools
- Built into GitHub: GitHub auto-generated release notes list the pull requests merged since the previous release when you draft a release. A
.github/release.ymlfile groups them by label. Free, no setup. - GitHub Actions and CLIs: Release Drafter keeps a draft release updated from merged PR titles. release-please and semantic-release also pick the next version from Conventional Commits. git-cliff renders a
CHANGELOG.mdfrom a template. All are open source and written for developers. - Hosted AI tools: Engammo, ReleasePad and ReleaseRay connect to GitHub and write the notes with AI instead of listing titles.
- Announcement platforms: LaunchNotes and similar tools give product and marketing an editor and release pages, but people write each post.
For a tool-by-tool guide to the free options, read the best tools to generate release notes from GitHub pull requests.
How Engammo delivers it
Process
- Install the Engammo GitHub App and pick the repositories to watch.
- Keep merging pull requests as usual. There are no workflow files, templates, commit conventions or CI pipeline changes.
- When a PR merges, GitHub sends a webhook. Engammo reads the PR title, description, labels and a trimmed summary of the changed files.
- AI writes a title of up to 80 characters that states the benefit, a one-sentence description and 3 to 5 bullets in plain language.
- The note is tagged from your labels (features, fixes, breaking changes, security, docs and more) and published within seconds.
- Anyone on the team can edit, regenerate or hide a note from the dashboard.
Where the release notes go
- A hosted updates page, public for customers or internal for signed-in workspace members.
- An embeddable widget you add to your product or help center with one script tag.
- An RSS feed and read-only public JSON endpoints.
- Versioned release notes that compile every change between two Git tags.
- Generated FAQs synced to a Kommander assistant, on the Team plan.
Stack, timeline and pricing model
Engammo works with public and private repositories on GitHub.com, including GitHub Enterprise Cloud. Setup takes a few minutes, and each note is ready within seconds of the merge. Pricing is a monthly subscription: Starter is $29/month for up to 3 repositories, and Team is $79/month for up to 10 repositories, with Italian and Spanish translations, no Engammo branding and Kommander sync. Both include unlimited release notes and AI summaries and a 14-day free trial. Enterprise pricing is custom. See pricing or how it works.
Use cases
A customer-facing changelog that never falls behind
SaaS teams embed the widget in their product and link the public updates page from the help center. Every merged PR becomes an entry, so the changelog covers every change instead of the ones someone remembered at the end of the sprint.
Internal updates for support, sales and product
Support and sales follow the internal updates page or the RSS feed to see that a fix or feature is live without asking engineering. Read more in how to keep non-technical teammates updated on what engineering shipped.
Versioned release notes for each tag
Teams that ship versions generate one release note from all the changes between two Git tags, ready for a launch post, a customer email or a leadership update.
Proof
Engammo is built by Gorilli, a software studio based in Italy, and launched in 2026. You can follow what we ship on the Engammo changelog, and see how a pull request becomes a plain-language note in how AI understands pull request context.
Engammo vs the alternatives
| Tool | How notes are created | AI-written | Where notes appear | Setup and cost |
|---|---|---|---|---|
| Engammo | A note for every merged PR, from its title, description, labels and changed files | Yes | Updates page, widget, RSS, JSON, versioned notes | Install the GitHub App; from $29/month after a 14-day free trial |
| GitHub auto-generated release notes | Lists merged PR titles and contributors since the previous release | No | GitHub Releases | None; built into GitHub |
| Release Drafter | Keeps a draft release updated from merged PR titles, grouped by label | No | GitHub Releases | Workflow file plus YAML template; open source |
| release-please | Release pull request with the version bump and CHANGELOG.md, from Conventional Commits | No | CHANGELOG.md, GitHub Releases | Commit convention plus config; open source |
| ReleasePad | AI drafts from merged work that you approve before publishing | Yes, on the Pro plan | Public changelog page, in-app widget | Install its GitHub App; free plan with limited posts, Pro at $35 per product per month |
| LaunchNotes | Announcements written and managed by product and marketing | No | Public and internal release pages, subscriber notifications | Built for larger product organizations |
| AI step in GitHub Actions | Your own workflow sends PR data to a model with your prompt | Yes | Whatever your workflow writes | Workflow, prompt, API key and ongoing maintenance |
Many teams combine them: an open source tool for the developer changelog and versioning, plus Engammo for release notes that customers and teammates can read. For more comparisons, see the best alternatives to Release Drafter, LaunchNotes alternatives for small teams and the best changelog tools for SaaS teams.
How to choose
- Who reads the notes? Developers are well served by GitHub's built-in notes or Release Drafter. Customers and non-technical teammates need plain language.
- Does it cover every change? Tools that work from merged pull requests cover every change by default. Editors depend on someone writing each post.
- Where are the notes published? GitHub Releases, or a page, widget and feed your readers already use.
- What does it access? Check which repositories it can read and what it stores. Engammo's approach is on the security page.
Ready to stop writing release notes by hand? See how Engammo works or start the 14-day free trial.
Frequently Asked Questions
What are the best tools to generate release notes from GitHub pull requests?
For developer changelogs, GitHub auto-generated release notes, Release Drafter and release-please are free and widely used. For plain-language release notes that customers and teammates can read, Engammo is a GitHub App that writes a note with AI for every merged pull request and publishes it to an updates page, widget and RSS feed.
How much does a tool to generate release notes from GitHub pull requests cost?
GitHub auto-generated release notes are free, and Release Drafter, release-please, semantic-release and git-cliff are open source. Engammo Starter is $29/month for up to 3 repositories and Team is $79/month for up to 10 repositories, both with unlimited release notes and AI summaries and a 14-day free trial. Enterprise pricing is custom.
How long does it take to set up?
Engammo takes a few minutes: install the GitHub App and pick your repositories. There are no workflow files or CI changes, and each release note is ready within seconds of the pull request merging.
How do I choose the right tool or partner to generate release notes from GitHub pull requests?
Check who reads the notes, whether the tool covers every change without someone remembering, where it publishes the notes and what repository data it accesses and stores. Developer tools fit engineering readers, while AI tools such as Engammo fit customers and non-technical teammates.
What makes Engammo different from a typical agency?
Engammo is a product, not an agency. Nobody needs to brief a writer: it reads each merged pull request and writes the release note on its own, for a monthly subscription instead of a project fee. Your team keeps control and can edit, regenerate or hide any note.
How do you handle security and data?
Engammo does not clone or index your repositories and does not store raw diffs. It stores the generated note and PR metadata such as title, description, labels, authors and timestamps. When AI summaries are on, selected diff excerpts are sent to the AI provider to write the summary. Data is encrypted in transit with TLS and at rest.