Bitbucket Integration
The Bitbucket integration uses OAuth. VULQN connects to a workspace, creates a workspace webhook for pull request events, syncs repositories, and lets you choose which repositories should be reviewed.
Connect Bitbucket
- Open Onboarding or Settings -> Add provider in VULQN.
- Choose Connect Bitbucket.
- Authorize VULQN in Bitbucket.
- Select the workspace to monitor.
- If the workspace is not listed, enter the workspace slug manually.
- Return to VULQN after the connection completes.
After setup, VULQN syncs repositories from the selected workspace. Enable only the repositories where reviews should run.
Enable repositories
In Settings:
- Find the Bitbucket connection.
- Use Sync repos if the list is stale.
- Enable the repositories VULQN should review.
- Confirm the branch field. New repositories default to
main,master. - Turn on peer review only for repositories that need it and have peer credits available.
Bitbucket events VULQN responds to
VULQN creates a workspace webhook for:
- Pull request created.
- Pull request updated.
- Pull request comment created.
- Pull request comment updated.
- Pull request fulfilled.
- Pull request rejected.
Those events allow VULQN to review new PRs, re-review updated PRs, process !vulqn commands, track comment-thread resolution, and update merged or closed review status.
OAuth workspace access
The Bitbucket setup flow discovers workspaces from your authorized account and also supports manual workspace slug entry. Manual entry is useful when Bitbucket does not return a workspace in the discovery list but your account can still access it.
VULQN stores the connection for the selected workspace. It does not review every synced repository by default; review coverage is still controlled from Settings.
Webhook setup errors
If Bitbucket blocks webhook creation, VULQN cannot receive pull request events for that workspace. The most common cause is missing webhook permission on the OAuth consumer that backs the VULQN integration.
If setup fails with a webhook-scope message, reconnect after the OAuth permissions are corrected.
Troubleshooting
| Problem | What to check |
|---|---|
| Workspace is not listed | Enter the workspace slug manually on the workspace selection screen. |
| Repositories are missing | Use Sync repos in the Bitbucket connection section. |
| PRs are not reviewed | Confirm the repository is active and the target branch matches the branch filter. |
| Connection was revoked | Reconnect Bitbucket from onboarding or settings. |
For PR comment commands, see !vulqn Commands.