Bitbucket
Architecture feedback on pull requests
Connect Bitbucket Cloud with an OAuth consumer or a workspace access token, and ArchPilot leaves inline comments on pull requests while findings land in your panel.
Auth: OAuth consumer or access token
Screens from a running installation
How it connects
- 01
Connect
Register an OAuth consumer in your workspace settings, or paste a workspace or repository access token.
- 02
Choose repos
Select the repositories to review.
- 03
Open a PR
ArchPilot reviews the diff and comments.
What you get
PR comments
Inline finding plus suggested fix.
Tokens refresh themselves
OAuth access tokens are short-lived; AppArch refreshes them before every call, so a review never fails on an expired token.
Findings in the panel
Score, trends and detail in one place.
Runs in your CI
Analysis runs in your Bitbucket Pipelines.
How it works inside AppArch
Your AppArch server talks to the Git platform; the analysis runs in your CI. Here is every call in both directions.
What it reads
- Repositories, branches and members; members every 10 minutes for Developer Sync
- Merge requests, approvals and review threads; MR facts every 15 minutes for MR Insights
- Branch protection and merge settings, for Git Health
- Single files and the file tree, for Compliance; nothing is cloned
What it writes
- Inline comments on the lines the change added
- An AppArch section in the MR description, or one summary comment if that edit fails
- Resolves its own thread once the finding is gone
- Optional auto-approve or auto-reject; it refuses to approve if new commits arrived after the review
- Starts the custom pipelines apparch-scan and apparch-manual, and can read and write pipeline variables
What it never does
- No commit statuses or check runs: the pipeline result is your CI job's own exit code
- Never clones or uploads the repository to the panel
- Never registers webhooks itself; paste the URL if you want one
- Bitbucket Cloud only; Server and Data Center are not supported
- Tag protection, release tracking and merge-gate rules are not read
An OAuth consumer (account, repository, pullrequest, webhook) whose roughly two-hour tokens are refreshed automatically, or a workspace or repository access token.
When things happen
- 5 sComments are posted
- 10 sNew findings are matched to their threads
- 5 minMerge request state and approvals are re-read
- 10 minMembers are synced
- 15 minMR facts for MR Insights
A webhook makes the merge request state change immediate instead of waiting for the next poll.
See it in the product
All screenshots
Connect Bitbucket
Connect in minutes - your first review lands on the next change.