GitHub Changelog Generator
Shipstar generates changelogs directly from your GitHub activity. Connect your account, pick the repositories to track, and every release cycle Shipstar reads the commits and merged pull requests and drafts a changelog entry that explains what shipped in language your users understand. No YAML config, no commit-message conventions, no manually curating a CHANGELOG.md before every release.
Connect GitHub in Minutes
Authorize Shipstar with GitHub OAuth, choose which repositories to track, and you're done — public and private repos both work. There's nothing to install in your CI pipeline and no webhook configuration to maintain. Shipstar fetches commit and pull request activity from the repositories you selected, so your changelog always reflects what actually merged, not what someone remembered to write down.
A Changelog Generator That Reads Commits and Pull Requests
Template-based changelog tools just reformat your commit messages — if the messages are cryptic, the changelog is too. Shipstar generates changelog entries from commits and pull requests using AI: it reads the actual changes, pulls context from PR descriptions, groups related work, and writes a summary aimed at users. A branch with forty commits and three merged PRs becomes a handful of clear bullet points about what's new.
Works with Real-World Git History
Squash merges, merge commits, fixup commits, 'wip' and 'address review comments' — real repositories are messy. Because Shipstar summarizes rather than parses, it handles messy history gracefully. Track multiple repositories in a single project and the generator combines activity across them, which makes it practical for monorepos, microservices, and teams that split frontend and backend across repos.
From Merged PR to Published Changelog
Generation is half the job — distribution is the other half. Every generated entry goes through a review step where you can edit before approving. Approved entries publish to your hosted changelog page, the embeddable changelog widget on your own site, RSS, email subscribers, Slack channels, and X. Your GitHub activity becomes a complete communication pipeline, not just a markdown file.
Why teams choose Shipstar
- Generate changelogs from GitHub commits and pull requests with one integration
- No commit conventions, CI config, or templates required
- Track multiple repositories and combine them into a single changelog
- Publish approved entries to your changelog page, email, Slack, and X automatically
Frequently asked questions
Does the GitHub changelog generator work with private repositories?
Yes. Shipstar connects through GitHub OAuth, so it can generate changelogs from any repository you grant it access to — public or private. You choose exactly which repositories to track.
Can I generate a changelog from pull requests instead of individual commits?
Shipstar reads both. Pull request titles and descriptions usually carry the best user-facing context, so the generator leans on them heavily, while commits fill in the details. Squash-merged PRs work just as well as merge commits.
How is this different from GitHub's auto-generated release notes?
GitHub's built-in release notes list PR titles verbatim. Shipstar rewrites your activity into prose aimed at users, filters out internal changes, applies your brand voice, and then distributes the result to your changelog page, email subscribers, and social channels — not just a GitHub release.
Does it support monorepos or multiple repositories?
Yes. You can track several repositories in one Shipstar project and generate a single changelog that covers all of them — useful for monorepos, microservice fleets, or separate frontend and backend repos.
Explore more
Explore related pages
Ship it. Share it. Celebrate it.
Release notes on autopilot.
Free to start. Connect your repo in 30 seconds.
No credit card required · Setup in 30 seconds