Bitbucket Server / Data Center support

[BerkayClik]

Problem

T3 Code's Bitbucket integration only speaks the Bitbucket Cloud API (https://api.bitbucket.org/2.0, /2.0/repositories/{workspace}/{repo}/...). Repositories hosted on a self-hosted Bitbucket Server / Data Center instance (e.g. https://bitbucket.example.com/scm/<project>/<repo>.git) get no pull-request support at all. The pull-request browser, PR sync, branch PR status and PR creation either don't work or, until #14591 is fixed, send requests to bitbucket.org for a repository that lives elsewhere.

The triage on #14591 confirmed that Server / Data Center support would be a separate feature and that no existing issue tracks it, so I'm opening this to ask whether you'd want it and in what scope.

What Server / Data Center differs on

• API: REST 1.0, /rest/api/1.0/projects/{KEY}/repos/{slug}/pull-requests/..., rather than Cloud's /2.0/repositories/{workspace}/{repo}/pullrequests/....
• Remote URL shapes: https://host/scm/{project}/{repo}.git and ssh://git@host:7999/{project}/{repo}.git.
• Pull request URLs: https://host/projects/{KEY}/repos/{slug}/pull-requests/{n}.
• Auth: instance-scoped HTTP access tokens (bearer), separate from any Bitbucket Cloud credential.
• Base URL: one per host, derived from the remote rather than one process-wide API root.

Proposed direction

A separate Bitbucket Server / Data Center client, chosen per host, similar in spirit to how self-hosted GitLab is scoped to the remote's host:

1. Detect Server / Data Center remotes and keep them apart from Bitbucket Cloud.
2. Per-host base URL and a per-host access token, so a Cloud token is never sent to a self-hosted instance (and vice versa).
3. Start with read support (list / view pull requests, branch PR status), then add actions (comment, approve, merge) if that goes well.

Questions for maintainers

• Is Bitbucket Server / Data Center something you'd accept, or would you prefer it stays out of core?
• If yes, is a read-only first step an acceptable scope?
• Any preference for how per-host credentials should be configured (Settings → Source Control vs. environment variables)?

[juliusmarminge]

Note

Grok responding on behalf of Julius.

Closing as a duplicate of #10837 — that Ideas thread already tracks Bitbucket Server / Data Center support (Cloud-only API today; different endpoints for self-hosted). Please continue the conversation there.

Related bug (misrouting self-hosted remotes to api.bitbucket.org) remains tracked separately at #14591.