Code integration
Bitbucket and Pacia
Bitbucket repositories connect read-only and are normalised into the same pull request model as GitHub, GitLab and Azure DevOps, so teams spanning several providers are still comparable on one set of definitions.
What Pacia reads from Bitbucket
Pull requests, reviewers, comments and merges
Repository and workspace metadata
Connecting it
Create read-only credentials 2 min
Generate an access token scoped to read your repositories and pull requests.
Connect in Pacia 1 min
Add the workspace, repository and token on the Providers page.
Let the backfill run ~15 min
History pages through per repository, up to 180 days.
Limits, stated up front
Every integration page on this site lists what the integration does not do. Finding that out during a trial is worse for both of us than finding it out now.
Refreshes on the 20-minute reconcile cycle or on demand rather than by live webhook.
Credentials are encrypted at rest and never returned in any API response.