Skip to content

Commit edffe14

Browse files
Gerwin Bisschopclaude
andcommitted
docs: mention Bitbucket user read scope needed by auth probe
The Bitbucket auth probe calls GET /2.0/user, which requires the read:user:bitbucket scope on scoped Atlassian API tokens. A token created with only the documented pull request + repository scopes passes every PR operation but fails the probe with a 403, so Settings -> Source Control shows the provider as not authenticated. Mention the extra scope in the install hint and the user docs. Fixes #6290 Co-Authored-By: Claude Fable 5 <[email protected]>
1 parent 5a84614 commit edffe14

2 files changed

Lines changed: 3 additions & 2 deletions

File tree

‎apps/server/src/sourceControl/BitbucketSourceControlProvider.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -195,7 +195,7 @@ export const makeDiscovery = Effect.gen(function* () {
195195
kind: "bitbucket",
196196
label: "Bitbucket",
197197
installHint:
198-
"Set T3CODE_BITBUCKET_EMAIL and T3CODE_BITBUCKET_API_TOKEN on the server (use a Bitbucket API token with pull request and repository scopes).",
198+
"Set T3CODE_BITBUCKET_EMAIL and T3CODE_BITBUCKET_API_TOKEN on the server (use a Bitbucket API token with pull request, repository, and user read scopes).",
199199
probeAuth: bitbucket.probeAuth,
200200
} satisfies SourceControlApiDiscoverySpec;
201201
});

‎docs/user/source-control.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,8 @@ export T3CODE_BITBUCKET_ACCESS_TOKEN="your-access-token"
9494
```
9595

9696
Or an Atlassian account email plus API token, with read/write access to pull requests and
97-
repositories:
97+
repositories, plus read access to your user account (`read:user:bitbucket`, used to verify the
98+
connection):
9899

99100
```bash
100101
export T3CODE_BITBUCKET_EMAIL="[email protected]"

0 commit comments

Comments
 (0)