Integrations
Tags become entries.
.md becomes guides.
Connect a Bitbucket Cloud workspace once. Drumroll syncs your repository tags into changelog entries and your Markdown files into a guides surface. Same OAuth, two distinct sync paths.
How it works
Three steps,
under five minutes.
- 01
Connect Bitbucket
Standard OAuth 2.0. Repository read scope. Refresh tokens are stored, so reconnects are automatic - no 60-minute reconnect dance.
- 02
Configure your repo
Tell Drumroll which repository, which branch, and where your changelog and guides .md files live (defaults: changelog/ and docs/).
- 03
Sync each source
Three buttons: Tags → entries, .md changelog → entries, .md guides → guides. Run them whenever you ship.
What syncs
Capabilities & limits.
We’re explicit about what Bitbucket 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
- Bitbucket Cloud OAuth 2.0 with refresh tokens
- Tag sync - one changelog entry per Git tag, ordered by commit date
- Markdown changelog sync with YAML-ish frontmatter (title, date, tags, status)
- Markdown guides sync with parent/child nesting via filename or order frontmatter
- Orphan cleanup - guides whose .md file disappears get removed on next sync
- Exponential backoff on rate limits with Retry-After support
- Per-file resilience - malformed frontmatter doesn't fail the run
Not yet supported
- Bitbucket Server / Data Center (on-premise)
- Webhook-driven syncs (on-demand by design)
- Branch protection / commit signing rules - sync is read-only
- Cross-repo aggregation - one repo per workspace currently
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