Integrations
Bitbucket
Dun reads your Bitbucket repositories and their branches/commits/files to resolve what to deploy.
Connect with an API tokenCode1 product
Note
Every mutating action — a deploy, a scale, a secret rotation, a DNS change — surfaces a plan in chat first. Dun never touches your Bitbucket resources until you approve it.
How to connect
Connect once from Integrations → Bitbucket, then toggle on the products you want Dun to manage.
1
Step 1
Click Connect with Bitbucket to authorize via OAuth — or open Bitbucket → Personal settings → App passwords for an access token.
2
Step 2
Grant the repository, repository:write, and pullrequest:write scopes DunOps needs.
3
Step 3
Paste the token below (or finish the OAuth flow) and click Connect.
Where to get credentials: https://bitbucket.org/account/settings/app-passwords/
What Dun can do
Each product below is something you can turn on. The examples are real prompts you can type in a chat thread.
Repositories
Read repository metadata and file contents, and commit approved changes back to a branch — the source surface the auto-fix loop uses.
Type in a chat thread
List my Bitbucket repositories
What's the head commit on develop in my app repo?| Permission | Required | What it does |
|---|---|---|
| List repositories | Yes | Names, default branch, and visibility of each repository. |
| Read files, branches, and commits | Yes | Resolve source context for diagnosis — read-only. |
| Commit approved fixes | Yes | Every write is gated by a chat approval; nothing is committed silently. |