Connect Bitbucket and the Coder reads your repository, its pull requests, and its issues, does the work in its own workspace, and hands you a pull request for review.
In Bitbucket, create a repository or workspace access token that can read and write the repository and its pull requests. Or create an Atlassian token or app password to use together with your account name.
Pushing and merging follow your house rules. The work becomes a pull request for review, a draft by default on a first run. If your house rules allow it, the Coder can also merge. Pushing a branch waits for your Approve unless your house rules allow it. See approvals.
Your token stays with your StellarFirm workspace and is never shown back to you. The page shows only that it is connected.
The account name is needed only with an Atlassian token or app password, not with a repository or workspace access token.
If the clone fails, the job stops as Blocked before any coding and says what to fix.
Coder, Bitbucket is connected. Pick up the top open issue on [workspace]/[repository], implement it, and open a pull request for review once I Approve.
PromptSummarise open pull requests
Coder, list the open pull requests on [workspace]/[repository], say which ones are stuck, and what each is waiting for.
PromptCheck a build
Coder, read the latest build results on [workspace]/[repository] and tell me whether the main branch is healthy.