Bitbucket Data Center
Where to start?
Follow the Qodo Aware setup guide to complete the initial configuration.
If you are using Bitbucket Data Center for version control, continue with this guide for the next steps.
Limitations
Individual repository selection is not supported. Qodo Aware will index all repositories visible to the token. To limit scope, create a token tied to a workspace or user with restricted access.
Webhooks and marketplace apps are not used. Bitbucket Cloud integration is token-only. No webhooks or Atlassian Connect app setup is required.
Step 1: Generate an Access Token
Qodo Aware supports two types of authentication for Bitbucket Cloud:
Workspace Access Token (Recommended)
Personal App Password (Alternative)
Both must use read-only scopes.
Option 1: Workspace Access Token (Recommended)
Prerequisite: You must be a Workspace Administrator.
Steps:
In Bitbucket, go to: Workspace settings ▸ Access management ▸ Access tokens
Click Create access token
Fill out the form:
Name: e.g.,
qodo-aware
Permissions:
Repositories:
Read
Projects:
Read
Pull requests:
Read
Click Create, then copy the token immediately. It will only be shown once.
Option 2: Personal App Password (Alternative)
Click your avatar ▸ Personal settings ▸ App passwords
Click Create app password
Set a name like
qodo-aware
Enable the following read-only scopes:
Repositories:
Read
Projects:
Read
Pull requests:
Read
Generate the password and copy it immediately. It will not be shown again.
Step 2: Configure Qodo Aware
In your .secrets.toml
file, add the following section. Do not duplicate existing provider blocks.
[bitbucket_data_center]
base_url = ""
webhook_secret = ""
bearer_token = ""
[config]
git_provider = "bitbucket_data_center" # or bitbucket_cloud, github_app, etc...
Notes:
Only one token per line.
You may mix workspace and personal tokens if needed.
Avoid duplicating the
[bitbucket_cloud]
section.
Last updated
Was this helpful?