Skip to content

OP2-293: Bitbucket Cloud behind the code tools, as another ICodeProvider - #20

Draft
BrewingCoder wants to merge 1 commit into
mainfrom
op2-293-bitbucket
Draft

BrewingCoder wants to merge 1 commit into
mainfrom
op2-293-bitbucket

Conversation

@BrewingCoder

Copy link
Copy Markdown
Owner

Work in progress. This is a draft, checkpointed early. Implements OP2-293: Bitbucket Cloud as another ICodeProvider behind the existing github_* code tools.

Done

  • BitbucketService (ICodeProvider, over api.bitbucket.org/2.0, one workspace per connection).
  • BitbucketConnectionService: an Atlassian API token, sent as Bearer, or as Basic with an optional email. The probe has separate sentences for a rejected credential, a workspace that doesn't exist, and no repositories.
  • ProviderKind.Bitbucket. It's stored by name, so there's no migration.
  • Capabilities: code.read is on and code.write is off.
  • DI, the bitbucket HTTP client, the add/check/replace-token endpoints, the add-connection form, and the repo-names filter.
  • CodeTools accepts Bitbucket connections. Triage now catches the provider exception and prints provider notes. github_pull_requests prints a provider's scope mapping.
  • It builds.

Left

  • Mocked-HTTP tests (BitbucketTests.cs), the full test run, and HostileToolSurfaceTests.
  • The final PR body: approach, auth choice, differences table, triage decision, and test results.

Generated by Claude Code

…, web, tools)

Builds; tests not yet written.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7auris7aiG4VxGYpBMpuT
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant