docs: mention Bitbucket user read scope needed by auth probe - #6291
docs: mention Bitbucket user read scope needed by auth probe#6291thamrx wants to merge 1 commit into
Conversation
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 pingdotgg#6290 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ApprovabilityVerdict: Approved edffe14 Documentation-only changes: updates an error message string and markdown docs to mention the additional You can customize Macroscope's approvability policy. Learn more. |
Fixes #6290
The Bitbucket auth probe (
probeAuth) callsGET /2.0/user, which on scoped Atlassian API tokens requiresread:user:bitbucket. A token created with only the currently documented scopes (pull request + repository read/write) works for every actual PR operation but fails the probe with a 403, so Settings → Source Control reports the provider as not authenticated and the toggle stays disabled.This is a docs-only change (two lines):
installHintinBitbucketSourceControlProvider.tsnow says "pull request, repository, and user read scopes"docs/user/source-control.mdmentions theread:user:bitbucketscope and why it is neededSee the issue for the full 403 response body showing required vs. granted scopes.
🤖 Generated with Claude Code
Note
Low Risk
Docs-only wording change for Bitbucket token scopes; no runtime or auth logic is modified.
Overview
Documents that Bitbucket API tokens need the
read:user:bitbucketscope so auth probing can succeed.Updates the Bitbucket
installHintand source-control setup docs to include user read access alongside pull request and repository scopes. Without it, tokens that work for PR operations still failprobeAuth(GET /2.0/user) and leave the provider disabled in settings.Reviewed by Cursor Bugbot for commit edffe14. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Document
read:user:bitbucketscope requirement for Bitbucket auth probeAdds
read:user:bitbucket(user read) to the list of required API token scopes in both the source-control.md docs and theinstallHintreturned bymakeDiscoveryin BitbucketSourceControlProvider.ts. This scope is used to verify the Bitbucket connection during the auth probe.Macroscope summarized edffe14.