What Bitbucket unlocks
Bitbucket covers the same ground as the GitHub connector for teams on Atlassian’s stack.
It brings in:
- repositories across the workspaces you belong to
- repository name, description, and the README on the main branch
- recent open and merged pull requests with their titles and descriptions
How to connect Bitbucket
- Open Integrations in VDF AI.
- Choose Bitbucket.
- Select Connect and sign in to Bitbucket when prompted.
- Select Grant access on Bitbucket’s authorization page.
- Return to VDF AI and confirm the card shows Connected.
A Bitbucket OAuth consumer has to be registered by your administrator first.
Typical tasks after connecting
- summarise what changed across recent pull requests
- find which repository owns a service by searching READMEs
- draft release notes from merged pull request descriptions
Access you may approve
Your Bitbucket password is never seen by VDF AI. Reading covers workspace membership, repository metadata, the main-branch README, and pull request titles and descriptions. Source code beyond the README, commit history, and PR comments are left alone.
Reconnect or disconnect
Bitbucket issues short-lived tokens that renew on their own. Reconnect from the card when renewal fails, which usually means access was revoked on the Bitbucket side.
Disconnect when repository context is no longer wanted in VDF AI.
Troubleshooting
A repository does not show up
Access follows the approving account. A repository that account cannot open in Bitbucket is out of reach here too.
Pull requests seem incomplete
Only recent open and merged pull requests are read; older history is deliberately left out.