Repository navigation
Bitbucket and Azure DevOps as first-class forges #456
Description
What T3 Code and Cursor do
T3 Code's source-control surface is forge-agnostic (docs):
- GitHub via
gh, GitLab viaglab, Azure DevOps viaaz+ the devops extension, Bitbucket via access token / API token env vars. - One Settings → Source Control page that shows authenticated / missing / which account, plus a Rescan button.
- Clone from
owner/repoor a git URL for any of the four. Publish a local repo with no remote to any of the four. - PR/MR create, title/body rewrite, and comment edit work on GitHub, GitLab, and Bitbucket. Azure DevOps title/body only; comments stay read-only.
Cursor for iPhone/iPad added Bitbucket and Azure DevOps SCM in the 29 Jul 2026 mobile release (changelog).
Solenta today
Planboard, PR actions, and issue ingestion are GitHub-only (gh). #193 covers GitLab. Nothing mentions Bitbucket or Azure DevOps.
Why it matters
A lot of the teams that would pay for an orchestrator live on Bitbucket (Atlassian shops) or Azure DevOps (Microsoft shops). Cursor and T3 already meet them there. GitHub-native remains the differentiator for planboard-as-issues; the PR/clone/publish layer should not hard-code one forge.
Scope suggestion
Keep GitHub as the planboard source of truth. Add Bitbucket + Azure DevOps only for clone, publish, and PR create/status — the same slice T3 actually uses daily. Do not invent a second planboard. Pair with #193 (GitLab) and #427 (forge-outage resilience).
Round-19 leftover, filed in round 20.
Activity
currentbits commentedon Aug 18, 2026
Round 19 validation: Cursor added GitLab/Bitbucket/Azure DevOps support for team marketplace imports (2026-06-22) and Bitbucket + Azure DevOps repo support for cloud agents (2026-07-29). The enterprise forge triopoly (GitHub, GitLab, Bitbucket/ADO) is now table stakes at the top of the market; this issue stays correctly scoped.
currentbits commentedon Oct 18, 2026
Publish landed on branch
coder/fork-bitbucket-and-azure-devops-as-first-5a2c0f(e02bcf11, on top of the PR-backend checkpoint e6d5075).origin, the thread header shows Publish. It opens a dialog that only lists forges marked ready in Settings → Source Control.gh repo create --source . --remote origin --push. GitLab usesglab repo create, Azure DevOps usesaz repos create, and Bitbucket usesPOST /2.0/repositories/{ws}/{slug}. For those three, Solenta adds origin itself and runsgit push -u.git log -p HEAD). The old first-push fallback only scanned HEAD~1..HEAD.electron/test/publish.test.js(fake gh/glab/az, stubbed fetch, real push to a local bare repo) and a renderer test for the button and dialog. Full electron suite: 4773/4773 pass.currentbits commentedon Oct 18, 2026
Landed from Solenta thread "Fork: Bitbucket and Azure DevOps as first-class forges". Closed on merge.
Publish repos with no origin, and run interactive OpenCode turns on o…