A changelog that follows
your releases.
Authorize once, pick a repo, hit sync. Drumroll lists every GitHub Release on the repo and turns each one into a changelog entry - title, body, draft state, prerelease tag, all preserved.
How it works
Three steps,
under five minutes.
- 01
Authorize GitHub
Standard OAuth App flow. Scopes: repo (read public + private repos you have access to) and read:user. Tokens are AES-256 encrypted before they touch our database.
- 02
Pick a repo
Type the repo as owner/repo (e.g. acme/changelog). It must be a repo your GitHub account can read - public or private.
- 03
Sync on demand
Click Sync. Each GitHub Release becomes one changelog entry. Drafts stay drafts; pre-releases are tagged. Re-syncs update entries in place - no duplicates.
What syncs
Capabilities & limits.
We’re explicit about what GitHub sync handles and what it doesn’t. Most teams find the first list covers their actual use; the second is the part vendors usually hide.
Supported
- GitHub OAuth App authorization
- Public + private repos via the repo scope
- Release body rendered as markdown (links, code, lists, headings)
- Stable source-ref dedupe via release id - re-syncs update existing entries
- Drafts stay drafts; pre-releases auto-tag with 'pre-release'
- 429 / rate-limit aware - short waits honored, long ones surfaced cleanly
Not yet supported
- GitHub Enterprise Server (self-hosted) - Cloud only for v1
- Webhook-driven sync - on-demand by design
- Reading non-release files - for repo Markdown sync, use the Bitbucket integration for now
- Issue / PR sync - releases only
Try it on a real project.
Two minutes to sign up, one click to connect, your team’s shipping rhythm becomes a public page. Always free.
Create a workspace