Appearance
Bitbucket
Liddr reads repositories and pull requests from the configured workspace during ingest, and — for reverse sync — pushes branches and opens pull requests when a Forge build completes. Auth is an Atlassian API token (Basic auth: email + token), the same token type Jira and Confluence use — so it can reuse the Jira connection's email and token if those are already set.
What Liddr accesses
| Direction | Access |
|---|---|
| Ingest (read into your knowledge graph) | Read-only |
| Reverse sync (Liddr writing back) | Read & write — only when a Forge action publishes back to this source |
Setup
- In Atlassian: id.atlassian.com → Security → API tokens → Create API token with scopes, and select the Bitbucket scopes below. (App passwords also work but Atlassian removes them 2026-07-28 — use an API token.)
- In Liddr: Settings → Connections → Bitbucket, set the Workspace in Advanced settings (required — it scopes the ingest).
- Set the Atlassian email (or leave blank to reuse the Jira connection's email) and paste the token. For reverse sync also set the Bitbucket username — git push needs the username, not the email.
- Test, then run an Ingest.
Required scopes
Atlassian API token (recommended)
Ingest — minimum
- read:repository:bitbucket
- read:pullrequest:bitbucket
- read:account (lets Test resolve the authenticated user)
Reverse sync — additionally
- write:repository:bitbucket (push build branches)
- write:pullrequest:bitbucket (open / decline PRs)
TIP
The token account needs at least read access to the workspace's repos for ingest, and write (Developer-equivalent) for reverse sync. Don't grant admin:* or webhook scopes — Liddr never uses them.
Legacy app password (until 2026-07-28)
Ingest — minimum
- Repositories: Read
- Pull requests: Read
Reverse sync — additionally
- Repositories: Write
- Pull requests: Write
TIP
App passwords reach end-of-life on 2026-07-28 — migrate to an Atlassian API token before then. Set the Bitbucket username (not email) as the identity when using an app password.