What is a GitHub changelog generator?

A GitHub changelog generator uses repository activity as source material for product updates. Changelog Generator starts with merged pull requests, creates an editable customer-facing draft, and gives you a hosted place to publish it.

Does it copy GitHub pull requests directly to the changelog?

No. Pull requests provide the facts, but the generated draft is written for customers. You can edit the title, summary, and individual items before publishing.

Is this a GitHub Action?

No. Changelog Generator connects to GitHub to use merged pull requests as source material. It is a separate workflow for drafting and publishing customer-facing updates.

Can the changelog live on our own domain?

Yes. You can publish the public changelog on a custom domain and make updates available through a widget or RSS feed.

GitHub changelog generator

Turn merged GitHub pull requests into a changelog customers can read

Changelog Generator turns the work already documented in GitHub into a clear product update. Start with merged pull requests, review the AI draft, and publish a changelog your customers can follow.

Create your changelog See live changelog

Drafts grounded in merged PRs

Editable customer-facing copy

Hosted changelog, widget, and RSS

PostHog

Changelog for posthog/posthog

GitHub

April 30, 2026

Enhanced Features & User Experience

New Features

Property-Level Access Control: You can now hide sensitive event and person properties from other users in your PostHog project, ensuring that sensitive information like PII is protected.
Survey MCP Creation Fields: Survey creation is now more streamlined through MCP, allowing you to set display conditions, schedule, and more in one go.
Session Replay Cancellation: Users can now cancel in-flight session summaries, giving you more control over ongoing processes.

Improvements

Heatmaps Display: The issue where 'SCRIPT_PLACEHOLDER' showed on heatmaps has been resolved, providing a cleaner, more professional view.
Survey Targeting Conditions: AI survey targeting conditions are now generated more reliably across projects.

Why it matters

Shipping in GitHub should not end with an invisible release.

Pull requests hold the implementation history, but they are not an announcement plan. A GitHub changelog generator turns that history into an update that explains what changed and why it matters to customers.

Git history is written for the team

Commit messages and PR titles help collaborators ship. Customers need the outcome, context, and the next thing they can do.

Weekly updates become a manual chore

Collecting every merged PR after a release means the announcement is often the first thing a busy team skips.

A changelog needs a durable home

A customer-facing update should be easy to find, share, embed in the product, and revisit later.

Workflow

From merged PRs to an approved customer update.

Keep the engineering workflow in GitHub while giving the people who own customer communication a draft they can refine.

Step 1

Choose the repository and release window

Connect GitHub and select the merged pull requests that represent the work you want to communicate.

Step 2

Generate a customer-facing draft

Changelog Generator groups related work and translates implementation detail into plain-language product outcomes.

Step 3

Edit, publish, and share

Keep control of the final copy, then publish it to a hosted changelog, custom domain, widget, or RSS feed.

From PRs to a product update

Technical shipping history, rewritten for customers.

Merged pull requests

PR #412: Add saved views to the customer list
PR #417: Reduce duplicate notifications for account owners
PR #421: Improve export reliability for large workspaces

Generated draft

A faster way to return to the customers that matter

Customer lists are easier to revisit, account owners receive fewer duplicate notifications, and larger exports complete more reliably. The update explains the practical result without asking customers to decode pull request titles.

Save the customer views you return to most often.
See fewer duplicate account notifications.
Export larger customer lists with more confidence.

Use cases

Built for teams that ship in GitHub and communicate with people.

The best GitHub changelog is not a copied commit list. It is a reliable bridge between the work engineering shipped and the value customers receive.

Founders

Show steady product momentum without spending every release day writing an announcement from scratch.

Product managers

Turn completed work into an accurate update while the shipping context is still easy to verify.

Product marketers

Start with a factual draft, then shape the message for customers, launch channels, and the public changelog.

FAQ

Common questions.

What is a GitHub changelog generator?: A GitHub changelog generator uses repository activity as source material for product updates. Changelog Generator starts with merged pull requests, creates an editable customer-facing draft, and gives you a hosted place to publish it.
Does it copy GitHub pull requests directly to the changelog?: No. Pull requests provide the facts, but the generated draft is written for customers. You can edit the title, summary, and individual items before publishing.
Is this a GitHub Action?: No. Changelog Generator connects to GitHub to use merged pull requests as source material. It is a separate workflow for drafting and publishing customer-facing updates.
Can the changelog live on our own domain?: Yes. You can publish the public changelog on a custom domain and make updates available through a widget or RSS feed.

Related resources

Keep learning about release notes.

Generate release notes from GitHub pull requests

A practical workflow for turning completed PRs into an accurate release note draft.

GitHub release notes templates

Copy the templates for feature releases, fixes, and breaking changes.

GitHub changelog example

See how raw PR history becomes a customer-facing product update.

Changelog guide

A central guide to changelogs, release notes, templates, and automation.

Release notes templates

Copy the structure before Changelog Generator fills it in.

How to write release notes

A practical guide for turning shipped work into readable updates.

Start now

Turn the next release into a page customers can read.

Connect GitHub, generate the draft, edit the copy, and publish your public changelog from one place.

Create your changelog