You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(source-control): add Brnch (brnch.io) support
#21330
Brnch is a Git host built around agent-driven changes. T3 Code does not recognise it, so a project whose remote is on brnch.io reads as an unknown host: no provider row in Settings → Source Control, no changes on the Pull Requests page, no publishing or cloning, and link_pull_request cannot claim its change URLs.
Proposal
Add a @t3tools/source-control-brnch provider package, following the same shape as the GitCafe provider:
Sign-in and discovery through the brnch CLI (brnch auth status), the same way GitHub uses gh. No token field in Settings.
Repositories: list, create, and clone. Brnch's HTTPS remotes sit below /git/ (https://brnch.io/git/{owner}/{repo}.git), so remote keys drop that prefix and HTTPS and SSH clones resolve to one repository.
Changes (Brnch's pull requests): find, view, create, check out, plus list, comment, ready, close, reopen, and merge on the Pull Requests page. Drafts are shown as open and marked.
Not offered: diffs, reviews, reviewer requests, and moving a change back to draft, because the CLI has no commands for them. The capability flags say so, so the UI hides those controls.
URL detection for https://brnch.io/{owner}/{repo}/changes/{n}, scoped to brnch.io only.
Web and mobile icons, and a short section in the user docs.
Scope
One package plus the usual registration points (built-in drivers, client definitions, shared URL and remote parsing, icons, docs). No product defaults change. No existing provider is touched.
Status
Implemented and verified against a real brnch.io account in the web client; a PR will follow and be linked here. Brnch itself shipped the author-handle field this relies on, so no T3-side workaround is needed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
Brnch is a Git host built around agent-driven changes. T3 Code does not recognise it, so a project whose remote is on brnch.io reads as an unknown host: no provider row in Settings → Source Control, no changes on the Pull Requests page, no publishing or cloning, and
link_pull_requestcannot claim its change URLs.Proposal
Add a
@t3tools/source-control-brnchprovider package, following the same shape as the GitCafe provider:brnchCLI (brnch auth status), the same way GitHub usesgh. No token field in Settings./git/(https://brnch.io/git/{owner}/{repo}.git), so remote keys drop that prefix and HTTPS and SSH clones resolve to one repository.https://brnch.io/{owner}/{repo}/changes/{n}, scoped to brnch.io only.Scope
One package plus the usual registration points (built-in drivers, client definitions, shared URL and remote parsing, icons, docs). No product defaults change. No existing provider is touched.
Status
Implemented and verified against a real brnch.io account in the web client; a PR will follow and be linked here. Brnch itself shipped the author-handle field this relies on, so no T3-side workaround is needed.
All reactions