ReleasePad
Features
GitHub App · push → draft

The AI changelog generator
that reads your commits.

Install the GitHub App, pick your repos, and you're done — there's nothing else to configure. Every push turns into a draft changelog entry written in language your customers can read, not bump deps to 4.2.1. You review it and publish. Nothing goes out without you.

Install the GitHub App — free

No credit card, no API keys. Read-only access to the repos you choose.

git diff HEAD~5..HEAD 27 files
reports/ExportMenu.tsx
@@ -8,14 +8,31 @@
9+import { toCsv } from "@/lib/csv";
15-<MenuItem disabled>Export</MenuItem>
15+<MenuItem onClick={exportCsv}>
16+  Export as CSV</MenuItem>
dashboard/useDashboardData.ts
@@ -21,9 +21,14 @@
22-const data = await fetchAll();
22+const data = await fetchBatched(
23+  { parallel: true, cache: "swr" });
auth/session.ts
@@ -64,3 +64,9 @@
66+if (token.isExpiring) await renew();
reports/ExportMenu.tsx
@@ -8,14 +8,31 @@
9+import { toCsv } from "@/lib/csv";
15-<MenuItem disabled>Export</MenuItem>
15+<MenuItem onClick={exportCsv}>
🤖 ReleasePad AI Engine
What's New
New Today

Export Any Report to CSV

One click pulls your current view — filters, columns, and all — into a spreadsheet-ready file. It works on every report, so the numbers you see are the numbers you share.

Improved Today

Dashboards Load Twice as Fast

We rebuilt how dashboards fetch their data — requests now run in parallel and anything unchanged comes from cache. The difference is biggest on large accounts with a long history.

Fixed Today

No More Surprise Logouts

Sessions now renew quietly in the background before they expire, so you stay signed in until you actually choose to leave.

1
App to install
nothing to configure
2
Read-only permissions
contents & metadata
0
Auto-publishes
you always review
3
Draft languages
English, Spanish, French
How it works

How to generate your product changelog using GitHub

There's no pipeline to build and no webhook to wire up. Install the App, and after that the only thing you do per release is read a draft and click publish.

1

Connect GitHub to your product

Sign up with any method you like — GitHub isn't required. Once your product is created, connect it to GitHub with our GitHub Marketplace app and pick the repos and branch to draft from. No webhooks, keys, or config: that's the whole setup.

2

Every push becomes a draft

Each push to your selected branch is what triggers the release notes. The AI reads the commits, groups changes into Feature / Improvement / Fix, drops the noise, and writes in plain language a customer can read — not "bump deps to 4.2.1." See how the automation works.

3

Review and publish

You get an email when drafts are ready. Edit anything, then hit publish — your public changelog page and in-app widget both update at once.

What the App can actually see

Two read-only permissions, and nothing else. ReleasePad never writes to your repositories, never modifies code, and never touches a repo you didn't select. You can change or revoke access at any time from your GitHub settings under Applications, the same place you manage every other installed App.

Repository contents
Read — to see your commit messages
Metadata
Read — required of every GitHub App
Keeping noise out: the [skip] tag

Not every commit deserves a line in your changelog. Put [skip] anywhere in the message and the commit is stored but excluded from generation — no config file, no ignore patterns to maintain.

git commit -m "Update CI pipeline [skip]"
Draft controls

It writes in your voice, not a generic one.

Four settings under Settings → AI shape every future draft. Set them once and stop re-editing the same things every release.

Tone

Professional, Casual, or Technical. Pick the one that matches how you already talk to your users everywhere else.

Language

Drafts in English, Spanish, or French — generated in that language from the start, not machine-translated after the fact.

Detail level

Brief, Detailed, or Comprehensive. A one-line summary per change, or the full explanation of what moved and why.

Emoji style

None, Subtle, or Expressive. Because there is no universally correct answer to this and you shouldn't have to delete them by hand.

None of it is locked in. Every draft is fully editable before it goes out, and drafts are never auto-published — the AI removes the blank page, you keep the final say. If you also run Conventional Commits, we parse them for cleaner grouping, but nothing here requires it.

Generate, then distribute

The generator is half of it.

A CLI generator hands you a Markdown file and stops. When you approve a ReleasePad draft, that one action publishes to every surface at once — the hosted page your customers bookmark, the widget inside your product, RSS and JSON feeds, and a stable LLM-ready Markdown URL that AI assistants can fetch when someone asks them what changed in your product.

Why AI agents are reading your changelog
An automated convoy of machines building a structure on a lunar surface, illustrating a release pipeline that runs without manual work
Versus the alternatives

Generators write files. Changelog tools want you to write.

The open-source generators and the changelog SaaS tools each solve one half of this. Here's where each one actually stops.

  ReleasePad conventional‑changelog semantic‑release Beamer Canny
Reads your commits
Needs a commit format No Yes, strict Yes, strict n/a n/a
Rewrites for non-technical users You write it You write it
Publishes to users Page, widget, feeds CHANGELOG.md Git tag + release
Also handles versioning Yes
Cost Free tier · $35/mo Free Free Per-MAU tiers Tracked-user tiers

If a CHANGELOG.md is genuinely all you need, use the free generators — we say so in our three-methods comparison. For the SaaS side, see 7 best Beamer alternatives and 7 best Canny alternatives.

Who it's for

Best fit if your commits outpace your comms.

Teams shipping with AI tools

Where commit volume is up and commit quality is down. Reading the change beats parsing the message. See what AI coding tools see.

Solo founders and small teams

Nobody's job is comms, so the changelog is whatever's left at 11pm. Here it's already drafted. See the solo founder's stack.

Anyone who tried a CLI generator

And found the output was accurate but unreadable to customers, or that the commit linting never stuck across the whole team.

GitHub integration FAQ

Common questions

Built and maintained by the ReleasePad team · Last updated

An AI changelog generator reads your source history — commits, merged pull requests, diffs — and uses a language model to write the changelog entries for you, instead of parsing commit messages into a list. A traditional generator like conventional-changelog or git-cliff can only reformat what you already typed, so 'fix: null check in parser' stays 'fix: null check in parser'; an AI generator interprets it and can write 'Fixed a crash when importing files with empty rows' instead. ReleasePad's GitHub integration is that generator plus the part most tools leave out: publishing — the same draft goes to your public changelog page, your in-app widget, your feeds, and an LLM-readable Markdown endpoint from one review.

Create a ReleasePad account — any sign-up method works, GitHub isn't required. Once your product is created, connect it to GitHub with the ReleasePad Marketplace app and select the repositories and branch to draft from. That's the entire setup — no webhooks to create, no API keys to copy. From then on, every push to your selected branch is captured automatically and the AI drafts changelog entries for you to review and publish.

No. Conventional Commit prefixes are parsed when they're there and give you cleaner grouping for free, but they are not required. This is the main practical difference from generators like conventional-changelog or semantic-release, which produce poor output the moment commit discipline slips.

Never. Generated entries always land as drafts and you get an email when they're ready. You publish them yourself from the posts list, after editing anything you want to change. There is no auto-publish setting to accidentally leave on.

Include [skip] anywhere in the commit message. The commit is still stored, but it's excluded from AI generation. It's the right tool for CI config changes, typo fixes, and dependency bumps that nobody outside the team needs to hear about.

Two read-only permissions: repository contents, to read your commit messages, and metadata, which every GitHub App requires. ReleasePad never writes to your repositories, never modifies code, and never sees a repository you didn't select during installation.

Yes. Under Settings, AI you can set the draft language to English, Spanish, or French, alongside tone, detail level, and emoji style. Drafts are generated in that language from the start rather than machine-translated afterwards.

From your GitHub settings under Applications, the same place you manage every other installed App. You can narrow which repositories ReleasePad can see, switch between all repos and a specific selection, or uninstall entirely — without touching your ReleasePad account. Already-published changelog posts stay exactly as they are.

Yes. GitHub's built-in generator lists merged pull request titles and contributors on a Releases page aimed at developers. ReleasePad rewrites the same changes into plain language for customers and publishes them to a hosted changelog page, an in-app widget, and machine-readable feeds outside of GitHub.

Your next push can write itself.

Install the App, pick your repos, and your first AI-drafted changelog entry is waiting after the next deploy. Free to start, $35/mo per product — unlimited team members included — when you're ready to ship without limits.

Try me now!