Integrations
Your changelog as
code review.
Commit Markdown files to your repository. Drumroll renders them on a public page and as a sidebar-driven guides site. Your release notes get the same review process as your code.
How it works
Three steps,
under five minutes.
- 01
Connect Bitbucket
We use the same Bitbucket OAuth as the Tags sync. One connection, multiple sync paths.
- 02
Drop .md files in a folder
Configure changelog/ and docs/ paths (or whatever you prefer). Drop a Markdown file with frontmatter, commit, push, open a PR.
- 03
Sync after merge
Hit sync from the Drumroll dashboard once the PR lands. Files become entries (or guides). Re-syncs update by source path. Deleted files are cleaned up.
What syncs
Capabilities & limits.
We’re explicit about what Markdown repo 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
- Frontmatter parsing - title, date, tags, status, slug, order
- Filename-derived dates - 2026-05-09-v1.4.md works without frontmatter
- First H1 used as title fallback if no frontmatter title
- Source path stored as stable ref - re-syncs update in place
- Both changelog entries and guides supported from the same repo
- Orphan cleanup on guides - deleted .md files trigger guide removal
- Per-file isolation - one bad frontmatter doesn't fail the run
Not yet supported
- MDX with custom React components - plain CommonMark for now
- Cross-repo guides - one Bitbucket repo per workspace
- Image embeds via relative paths in repo (use absolute URLs)
- GitHub-hosted repos - Bitbucket only for v1
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