feat: add Gitea source-control provider

[MDragonryu]

Summary

• add Gitea discovery and authentication through tea
• implement repository, branch, pull-request, and provider operations
• wire Gitea through server, web, mobile, contracts, Git actions, and documentation
• add focused coverage for CLI parsing, provider behavior, registry discovery, and source-control contracts

Testing

• CI=true pnpm exec vp test run apps/server/src/sourceControl/GiteaCli.test.ts apps/server/src/sourceControl/GiteaSourceControlProvider.test.ts apps/server/src/sourceControl/giteaLogins.test.ts apps/server/src/sourceControl/SourceControlProviderRegistry.test.ts packages/shared/src/sourceControl.test.ts packages/contracts/src/sourceControl.test.ts
• 6 test files passed, 109 tests passed
• live validation completed against a fresh Gitea container with repository, commit/push, and three pull-request scenarios

Notes

Gitea support uses the authenticated tea CLI and preserves the existing provider architecture across server and clients.

---

Note

Medium Risk
Changes git stacked actions, PR creation/deduping, and remote provider resolution; behavior is heavily tested but errors could still mis-route remotes or mishandle tea HTTP responses.

Overview
Adds first-class Gitea support end-to-end so remotes no longer resolve to unknown and Commit, push & create PR works against Gitea hosts.

On the server, a new GiteaCli layer wraps the tea tool (API calls with HTTP status parsing because tea api exits 0 on errors, client-side PR list filtering/pagination, repo publish routing to user/repos vs orgs/.../repos). GiteaSourceControlProvider plugs into the existing registry with CLI discovery from tea logins list and host-based refinement of otherwise-unknown self-hosted remotes when tea is logged into that host.

Contracts, shared remote detection (gitea.com / *gitea* hosts), web and mobile add-project/publish/settings flows, and docs are extended for gitea. Publish UI uses discovery for hostname when there is no canonical host. In-app deep links still skip Gitea (parseChangeRequestUrl does not claim /pulls/{n}), while checkout/reference parsing accepts Gitea URLs and tea pulls checkout.

VcsProcess now treats tea’s “no available login” stderr as an authentication failure.

^{Reviewed by Cursor Bugbot for commit d1b9069. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Gitea source-control provider across backend, web, and mobile

• Implements GiteaCli wrapper around the tea CLI in GiteaCli.ts, covering PR list/get/create, repo creation, clone URLs, default branch, and checkout, with typed errors and HTTP status mapping.
• Adds GiteaSourceControlProvider in GiteaSourceControlProvider.ts implementing the provider contract, plus discovery and auth parsing based on tea logins list output.
• Wires Gitea into the server provider registry and WebSocket RPC layers in server.ts and ws.ts.
• Updates web, mobile, and shared packages: command palette, publish dialog, PR reference parsing, settings UI, icons, and provider detection.
• Risk: new 'gitea' literal added to SourceControlProviderKind schema in sourceControl.ts; out-of-tree contract consumers must regenerate schemas to decode the new kind.

^{Macroscope summarized d1b9069.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e4dce5a6-b2ec-4eb6-81ff-3ae86dc8f69e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Structure, namespace imports, Context.Service + inline interface, make/layer, and environment-based dependency acquisition all look right, and the test-only service-instance injection in GitManager.test.ts is a legitimate seam. Three findings on error modeling in apps/server/src/sourceControl/GiteaCli.ts.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI Consistency: 2 findings

Provider plumbing for the web client is otherwise complete and consistent (icon maps, labels, path hints, readiness, publish host, "Open on Gitea"). Two web surfaces that key off provider identity were not extended with the new kind, so Gitea users get different behaviour from every other host:

1. apps/web/src/lib/openPullRequestLink.ts (inline comment) — Gitea PR URLs are now readable for opening links, but apps/web/src/pullRequestReference.ts still rejects them for input, while the input placeholder promises "PR URL, checkout command, or #42".

2. apps/web/src/components/pullRequest/pullRequestDetail.logic.ts:855 — TOOL_NOISE replaces content-free host errors with an actionable hint for github|gitlab|bitbucket|azure devops, but the new provider's GiteaCliCommandError.detail is "Gitea CLI command failed." (apps/server/src/sourceControl/GiteaCli.ts:121), which no pattern matches. A failed Gitea action therefore surfaces the bare "Gitea CLI command failed." string where the other hosts surface the hint. Smallest fix is to include gitea in the alternation:

- /^(github|gitlab|bitbucket|azure devops)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,+ /^(github|gitlab|bitbucket|azure devops|gitea)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,

Minor, optional: the "Add project" command item's searchTerms (apps/web/src/components/CommandPalette.tsx:1547) lists github/gitlab/bitbucket/azure/devops but not gitea, so typing "gitea" no longer reaches the flow that now offers a Gitea source.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a large, cross-cutting Gitea integration with new authenticated repository, pull-request, checkout, and publishing workflows across production server and client paths. A remaining error-classification concern may cause missing pull requests to surface as generic command failures, so the runtime behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[MDragonryu]

Addressed the review findings in :\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout , and required a real NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[MDragonryu]

Addressed the review findings in commit 3e5118d:\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing tea executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout --force, and required a real tea login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Service definition, dependency acquisition (GiteaCli/GiteaSourceControlProvider both acquire their deps with yield* and expose make/layer), namespace imports, and the registry/layer wiring all look consistent with the sibling providers. Two error-modelling points below.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit 3f98c41:\n\n- createPullRequest no longer supplies a PR reference to HTTP error mapping, so a create-time 404 is a GiteaCliCommandError; existing get/checkout PR 404s remain not-found\n- listPullRequests now requests sort=recentupdate, keeping current-branch PR discovery within the bounded page window\n\nThe focused Linux devcontainer suite now passes 8 files and 164 tests.

[MDragonryu]

Follow-up Effect cleanup pushed in commit c0599af:\n\n- removed the redundant single-valued list decode operation field\n- removed the manufactured non-array JSON Error; decoder failures now carry the real schema failure while malformed JSON retains the real parse exception\n\nThe focused Linux devcontainer suite remains green: 8 files, 164 tests.

[macroscopeapp]

One finding: the new tea branch in classifyNonZeroExit changes backend error classification but has no focused test, and no tea rule produces not-found, so GiteaCli.checkoutPullRequest's not-found mapping is unreachable in production. Everything else in the new Gitea service modules follows the conventions (subpath namespace imports, inline Context.Service interface, make acquiring VcsProcess/GiteaCli from the environment, Schema.TaggedErrorClass errors with structural attributes and preserved cause, exported Schema.is predicate, layer at the bottom).

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

This changes backend failure classification (a tea exit mentioning "no available login" now surfaces as GiteaCliAuthenticationError rather than GiteaCliCommandError), but VcsProcess.test.ts has no case for it even though it already covers the analogous authentication and rate-limited phrases. Consider adding a focused case asserting failureKind: "authentication" for command: "tea" with that stderr, plus one asserting another command with the same phrase stays command-failed (the reason the rule is scoped to tea).

Related: no tea branch exists in the not-found block below, so classifyNonZeroExit never returns not-found for tea. GiteaCli.checkoutPullRequest's GiteaPullRequestNotFoundError.fromVcsError path is therefore only reachable in the unit test that hand-builds failureKind: "not-found"; a real tea pulls checkout 9999 failure maps to GiteaCliCommandError. Worth either adding the tea not-found phrases here or dropping the unreachable branch.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit d257b11:\n\n- full PR URL checkout now verifies the URL repository against the current Gitea repository before invoking tea, preserving same-repository and numeric checkout behavior\n- public github.com and bitbucket.org /pulls/ URLs are excluded from the generic Gitea reference parser while self-hosted lookalikes remain supported\n- added regression coverage for the repository guard and URL parsing\n\nVerification: 8 focused Linux devcontainer test files, 168 tests passed; targeted server/web TypeScript checks completed.

[macroscopeapp]

One new finding on the Gitea CLI error model, plus one earlier finding that is still open (see below). Everything else in the Gitea service/provider pair follows the conventions: namespaced effect/* imports, Context.Service with an inline interface, exported make/layer, dependencies acquired via yield* VcsProcess.VcsProcess / yield* GiteaCli.GiteaCli, structured Schema.TaggedErrorClass failures with real causes preserved and messages derived from stable attributes, and Schema.Union + Schema.is for the error predicate.

Still open from a previous run (not re-commented): apps/server/src/vcs/VcsProcess.ts changes non-zero-exit classification so a tea failure mentioning "no available login" is now categorized as authentication, and apps/server/src/vcs/VcsProcess.test.ts still has no case covering it (nor a case proving another command with the same phrase stays command-failed). Backend behavior changes should carry focused tests.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up test/convention fixes pushed in commit 556ce2d:\n\n- removed the redundant single-value Gitea pull-request decode operation field\n- added focused coverage for tea no-available-login authentication classification and the non-tea negative case\n\nVerification: 9 focused Linux devcontainer test files, 182 tests passed.

[macroscopeapp]

Reviewed the changed web UI surfaces for the Gitea provider addition (CommandPalette.tsx, GitActionsControl.tsx, SourceControlSettings.tsx, sourceControlPresentation.ts, pullRequestLinkContextMenu.ts, pullRequestDetail.logic.ts, openPullRequestLink.ts, pullRequestReference.ts). Provider enumerations, labels, icons and readiness maps are consistent, and the reference parser gap flagged on the earlier revision is now closed.

Two findings, one behavioral:

1. openPullRequestLink.ts now claims Gitea /pulls/{n} URLs, which makes those links open the in-app change-request surfaces even though this build registers no Gitea pull-request provider — the reader lands on the "Could not load pull requests" empty state instead of the host page they previously got in the browser.
2. GitActionsControl.tsx uses the literal "gitea" as the publish-dialog host, which is rendered as a hostname prefix when discovery reports no host.

^{Posted via Macroscope — UI Consistency}

[MDragonryu]

Final review cycle for 556ce2d is complete. Cursor Bugbot, Macroscope Correctness, Effect Service Conventions, and UI Consistency are green; the Approvability check completed neutral with correctness checked and eligibility unchecked. No new inline comments were posted on the current head. The worktree is clean and the PR is ready for human review.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16d32bc. Configure here.}

[macroscopeapp]

Two findings, both in the Source Control settings copy that this PR reworked to make room for Gitea's tea login add hint. The rest of the Gitea UI wiring (neutral GitPullRequestIcon for the unbranded provider, resolvePublishHost host fallback, /pulls/ link handling) looks consistent with the existing provider patterns.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

login add is a tea-only subcommand, but this helper renders the unauthenticated row for every provider, so GitHub now reads "Run gh login add", GitLab "Run glab login add" and Azure DevOps "Run az login add" — none of those commands exist (gh auth login, glab auth login, az login). The copy that was replaced was deliberately executable-agnostic.

Consider keeping the neutral phrasing here (or threading a per-provider auth command through the discovery spec) so only Gitea gets the tea login add wording:

Suggested change

	if(executable!==null){
	return`${label} is not authenticated on this server. Run \`${executable} login add\` on the server host to enable change request features.`;
	return`${label} is not authenticated on this server. Sign in or configure credentials using the \`${executable}\` tool on the server host to enable change request features.`;

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

We do not have a current support commitment for Gitea. This 39-file branch would add a source control CLI, discovery, repository operations, settings, contracts, icons, and a permanent compatibility obligation.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[MDragonryu]

Summary

• add Gitea discovery and authentication through tea
• implement repository, branch, pull-request, and provider operations
• wire Gitea through server, web, mobile, contracts, Git actions, and documentation
• add focused coverage for CLI parsing, provider behavior, registry discovery, and source-control contracts

Testing

• CI=true pnpm exec vp test run apps/server/src/sourceControl/GiteaCli.test.ts apps/server/src/sourceControl/GiteaSourceControlProvider.test.ts apps/server/src/sourceControl/giteaLogins.test.ts apps/server/src/sourceControl/SourceControlProviderRegistry.test.ts packages/shared/src/sourceControl.test.ts packages/contracts/src/sourceControl.test.ts
• 6 test files passed, 109 tests passed
• live validation completed against a fresh Gitea container with repository, commit/push, and three pull-request scenarios

Notes

Gitea support uses the authenticated tea CLI and preserves the existing provider architecture across server and clients.

---

Note

Medium Risk
Changes git stacked actions, PR creation/deduping, and remote provider resolution; behavior is heavily tested but errors could still mis-route remotes or mishandle tea HTTP responses.

Overview
Adds first-class Gitea support end-to-end so remotes no longer resolve to unknown and Commit, push & create PR works against Gitea hosts.

On the server, a new GiteaCli layer wraps the tea tool (API calls with HTTP status parsing because tea api exits 0 on errors, client-side PR list filtering/pagination, repo publish routing to user/repos vs orgs/.../repos). GiteaSourceControlProvider plugs into the existing registry with CLI discovery from tea logins list and host-based refinement of otherwise-unknown self-hosted remotes when tea is logged into that host.

Contracts, shared remote detection (gitea.com / *gitea* hosts), web and mobile add-project/publish/settings flows, and docs are extended for gitea. Publish UI uses discovery for hostname when there is no canonical host. In-app deep links still skip Gitea (parseChangeRequestUrl does not claim /pulls/{n}), while checkout/reference parsing accepts Gitea URLs and tea pulls checkout.

VcsProcess now treats tea’s “no available login” stderr as an authentication failure.

^{Reviewed by Cursor Bugbot for commit d1b9069. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Gitea source-control provider across backend, web, and mobile

• Implements GiteaCli wrapper around the tea CLI in GiteaCli.ts, covering PR list/get/create, repo creation, clone URLs, default branch, and checkout, with typed errors and HTTP status mapping.
• Adds GiteaSourceControlProvider in GiteaSourceControlProvider.ts implementing the provider contract, plus discovery and auth parsing based on tea logins list output.
• Wires Gitea into the server provider registry and WebSocket RPC layers in server.ts and ws.ts.
• Updates web, mobile, and shared packages: command palette, publish dialog, PR reference parsing, settings UI, icons, and provider detection.
• Risk: new 'gitea' literal added to SourceControlProviderKind schema in sourceControl.ts; out-of-tree contract consumers must regenerate schemas to decode the new kind.

^{Macroscope summarized d1b9069.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e4dce5a6-b2ec-4eb6-81ff-3ae86dc8f69e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Structure, namespace imports, Context.Service + inline interface, make/layer, and environment-based dependency acquisition all look right, and the test-only service-instance injection in GitManager.test.ts is a legitimate seam. Three findings on error modeling in apps/server/src/sourceControl/GiteaCli.ts.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI Consistency: 2 findings

Provider plumbing for the web client is otherwise complete and consistent (icon maps, labels, path hints, readiness, publish host, "Open on Gitea"). Two web surfaces that key off provider identity were not extended with the new kind, so Gitea users get different behaviour from every other host:

1. apps/web/src/lib/openPullRequestLink.ts (inline comment) — Gitea PR URLs are now readable for opening links, but apps/web/src/pullRequestReference.ts still rejects them for input, while the input placeholder promises "PR URL, checkout command, or #42".

2. apps/web/src/components/pullRequest/pullRequestDetail.logic.ts:855 — TOOL_NOISE replaces content-free host errors with an actionable hint for github|gitlab|bitbucket|azure devops, but the new provider's GiteaCliCommandError.detail is "Gitea CLI command failed." (apps/server/src/sourceControl/GiteaCli.ts:121), which no pattern matches. A failed Gitea action therefore surfaces the bare "Gitea CLI command failed." string where the other hosts surface the hint. Smallest fix is to include gitea in the alternation:

- /^(github|gitlab|bitbucket|azure devops)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,+ /^(github|gitlab|bitbucket|azure devops|gitea)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,

Minor, optional: the "Add project" command item's searchTerms (apps/web/src/components/CommandPalette.tsx:1547) lists github/gitlab/bitbucket/azure/devops but not gitea, so typing "gitea" no longer reaches the flow that now offers a Gitea source.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a large, cross-cutting Gitea integration with new authenticated repository, pull-request, checkout, and publishing workflows across production server and client paths. A remaining error-classification concern may cause missing pull requests to surface as generic command failures, so the runtime behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[MDragonryu]

Addressed the review findings in :\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout , and required a real NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[MDragonryu]

Addressed the review findings in commit 3e5118d:\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing tea executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout --force, and required a real tea login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Service definition, dependency acquisition (GiteaCli/GiteaSourceControlProvider both acquire their deps with yield* and expose make/layer), namespace imports, and the registry/layer wiring all look consistent with the sibling providers. Two error-modelling points below.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit 3f98c41:\n\n- createPullRequest no longer supplies a PR reference to HTTP error mapping, so a create-time 404 is a GiteaCliCommandError; existing get/checkout PR 404s remain not-found\n- listPullRequests now requests sort=recentupdate, keeping current-branch PR discovery within the bounded page window\n\nThe focused Linux devcontainer suite now passes 8 files and 164 tests.

[MDragonryu]

Follow-up Effect cleanup pushed in commit c0599af:\n\n- removed the redundant single-valued list decode operation field\n- removed the manufactured non-array JSON Error; decoder failures now carry the real schema failure while malformed JSON retains the real parse exception\n\nThe focused Linux devcontainer suite remains green: 8 files, 164 tests.

[macroscopeapp]

One finding: the new tea branch in classifyNonZeroExit changes backend error classification but has no focused test, and no tea rule produces not-found, so GiteaCli.checkoutPullRequest's not-found mapping is unreachable in production. Everything else in the new Gitea service modules follows the conventions (subpath namespace imports, inline Context.Service interface, make acquiring VcsProcess/GiteaCli from the environment, Schema.TaggedErrorClass errors with structural attributes and preserved cause, exported Schema.is predicate, layer at the bottom).

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

This changes backend failure classification (a tea exit mentioning "no available login" now surfaces as GiteaCliAuthenticationError rather than GiteaCliCommandError), but VcsProcess.test.ts has no case for it even though it already covers the analogous authentication and rate-limited phrases. Consider adding a focused case asserting failureKind: "authentication" for command: "tea" with that stderr, plus one asserting another command with the same phrase stays command-failed (the reason the rule is scoped to tea).

Related: no tea branch exists in the not-found block below, so classifyNonZeroExit never returns not-found for tea. GiteaCli.checkoutPullRequest's GiteaPullRequestNotFoundError.fromVcsError path is therefore only reachable in the unit test that hand-builds failureKind: "not-found"; a real tea pulls checkout 9999 failure maps to GiteaCliCommandError. Worth either adding the tea not-found phrases here or dropping the unreachable branch.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit d257b11:\n\n- full PR URL checkout now verifies the URL repository against the current Gitea repository before invoking tea, preserving same-repository and numeric checkout behavior\n- public github.com and bitbucket.org /pulls/ URLs are excluded from the generic Gitea reference parser while self-hosted lookalikes remain supported\n- added regression coverage for the repository guard and URL parsing\n\nVerification: 8 focused Linux devcontainer test files, 168 tests passed; targeted server/web TypeScript checks completed.

[macroscopeapp]

One new finding on the Gitea CLI error model, plus one earlier finding that is still open (see below). Everything else in the Gitea service/provider pair follows the conventions: namespaced effect/* imports, Context.Service with an inline interface, exported make/layer, dependencies acquired via yield* VcsProcess.VcsProcess / yield* GiteaCli.GiteaCli, structured Schema.TaggedErrorClass failures with real causes preserved and messages derived from stable attributes, and Schema.Union + Schema.is for the error predicate.

Still open from a previous run (not re-commented): apps/server/src/vcs/VcsProcess.ts changes non-zero-exit classification so a tea failure mentioning "no available login" is now categorized as authentication, and apps/server/src/vcs/VcsProcess.test.ts still has no case covering it (nor a case proving another command with the same phrase stays command-failed). Backend behavior changes should carry focused tests.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up test/convention fixes pushed in commit 556ce2d:\n\n- removed the redundant single-value Gitea pull-request decode operation field\n- added focused coverage for tea no-available-login authentication classification and the non-tea negative case\n\nVerification: 9 focused Linux devcontainer test files, 182 tests passed.

[macroscopeapp]

Reviewed the changed web UI surfaces for the Gitea provider addition (CommandPalette.tsx, GitActionsControl.tsx, SourceControlSettings.tsx, sourceControlPresentation.ts, pullRequestLinkContextMenu.ts, pullRequestDetail.logic.ts, openPullRequestLink.ts, pullRequestReference.ts). Provider enumerations, labels, icons and readiness maps are consistent, and the reference parser gap flagged on the earlier revision is now closed.

Two findings, one behavioral:

1. openPullRequestLink.ts now claims Gitea /pulls/{n} URLs, which makes those links open the in-app change-request surfaces even though this build registers no Gitea pull-request provider — the reader lands on the "Could not load pull requests" empty state instead of the host page they previously got in the browser.
2. GitActionsControl.tsx uses the literal "gitea" as the publish-dialog host, which is rendered as a hostname prefix when discovery reports no host.

^{Posted via Macroscope — UI Consistency}

[MDragonryu]

Final review cycle for 556ce2d is complete. Cursor Bugbot, Macroscope Correctness, Effect Service Conventions, and UI Consistency are green; the Approvability check completed neutral with correctness checked and eligibility unchecked. No new inline comments were posted on the current head. The worktree is clean and the PR is ready for human review.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16d32bc. Configure here.}

[macroscopeapp]

Two findings, both in the Source Control settings copy that this PR reworked to make room for Gitea's tea login add hint. The rest of the Gitea UI wiring (neutral GitPullRequestIcon for the unbranded provider, resolvePublishHost host fallback, /pulls/ link handling) looks consistent with the existing provider patterns.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

login add is a tea-only subcommand, but this helper renders the unauthenticated row for every provider, so GitHub now reads "Run gh login add", GitLab "Run glab login add" and Azure DevOps "Run az login add" — none of those commands exist (gh auth login, glab auth login, az login). The copy that was replaced was deliberately executable-agnostic.

Consider keeping the neutral phrasing here (or threading a per-provider auth command through the discovery spec) so only Gitea gets the tea login add wording:

Suggested change

	if(executable!==null){
	return`${label} is not authenticated on this server. Run \`${executable} login add\` on the server host to enable change request features.`;
	return`${label} is not authenticated on this server. Sign in or configure credentials using the \`${executable}\` tool on the server host to enable change request features.`;

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

We do not have a current support commitment for Gitea. This 39-file branch would add a source control CLI, discovery, repository operations, settings, contracts, icons, and a permanent compatibility obligation.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[MDragonryu]

Summary

• add Gitea discovery and authentication through tea
• implement repository, branch, pull-request, and provider operations
• wire Gitea through server, web, mobile, contracts, Git actions, and documentation
• add focused coverage for CLI parsing, provider behavior, registry discovery, and source-control contracts

Testing

• CI=true pnpm exec vp test run apps/server/src/sourceControl/GiteaCli.test.ts apps/server/src/sourceControl/GiteaSourceControlProvider.test.ts apps/server/src/sourceControl/giteaLogins.test.ts apps/server/src/sourceControl/SourceControlProviderRegistry.test.ts packages/shared/src/sourceControl.test.ts packages/contracts/src/sourceControl.test.ts
• 6 test files passed, 109 tests passed
• live validation completed against a fresh Gitea container with repository, commit/push, and three pull-request scenarios

Notes

Gitea support uses the authenticated tea CLI and preserves the existing provider architecture across server and clients.

---

Note

Medium Risk
Changes git stacked actions, PR creation/deduping, and remote provider resolution; behavior is heavily tested but errors could still mis-route remotes or mishandle tea HTTP responses.

Overview
Adds first-class Gitea support end-to-end so remotes no longer resolve to unknown and Commit, push & create PR works against Gitea hosts.

On the server, a new GiteaCli layer wraps the tea tool (API calls with HTTP status parsing because tea api exits 0 on errors, client-side PR list filtering/pagination, repo publish routing to user/repos vs orgs/.../repos). GiteaSourceControlProvider plugs into the existing registry with CLI discovery from tea logins list and host-based refinement of otherwise-unknown self-hosted remotes when tea is logged into that host.

Contracts, shared remote detection (gitea.com / *gitea* hosts), web and mobile add-project/publish/settings flows, and docs are extended for gitea. Publish UI uses discovery for hostname when there is no canonical host. In-app deep links still skip Gitea (parseChangeRequestUrl does not claim /pulls/{n}), while checkout/reference parsing accepts Gitea URLs and tea pulls checkout.

VcsProcess now treats tea’s “no available login” stderr as an authentication failure.

^{Reviewed by Cursor Bugbot for commit d1b9069. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Gitea source-control provider across backend, web, and mobile

• Implements GiteaCli wrapper around the tea CLI in GiteaCli.ts, covering PR list/get/create, repo creation, clone URLs, default branch, and checkout, with typed errors and HTTP status mapping.
• Adds GiteaSourceControlProvider in GiteaSourceControlProvider.ts implementing the provider contract, plus discovery and auth parsing based on tea logins list output.
• Wires Gitea into the server provider registry and WebSocket RPC layers in server.ts and ws.ts.
• Updates web, mobile, and shared packages: command palette, publish dialog, PR reference parsing, settings UI, icons, and provider detection.
• Risk: new 'gitea' literal added to SourceControlProviderKind schema in sourceControl.ts; out-of-tree contract consumers must regenerate schemas to decode the new kind.

^{Macroscope summarized d1b9069.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e4dce5a6-b2ec-4eb6-81ff-3ae86dc8f69e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Structure, namespace imports, Context.Service + inline interface, make/layer, and environment-based dependency acquisition all look right, and the test-only service-instance injection in GitManager.test.ts is a legitimate seam. Three findings on error modeling in apps/server/src/sourceControl/GiteaCli.ts.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI Consistency: 2 findings

Provider plumbing for the web client is otherwise complete and consistent (icon maps, labels, path hints, readiness, publish host, "Open on Gitea"). Two web surfaces that key off provider identity were not extended with the new kind, so Gitea users get different behaviour from every other host:

1. apps/web/src/lib/openPullRequestLink.ts (inline comment) — Gitea PR URLs are now readable for opening links, but apps/web/src/pullRequestReference.ts still rejects them for input, while the input placeholder promises "PR URL, checkout command, or #42".

2. apps/web/src/components/pullRequest/pullRequestDetail.logic.ts:855 — TOOL_NOISE replaces content-free host errors with an actionable hint for github|gitlab|bitbucket|azure devops, but the new provider's GiteaCliCommandError.detail is "Gitea CLI command failed." (apps/server/src/sourceControl/GiteaCli.ts:121), which no pattern matches. A failed Gitea action therefore surfaces the bare "Gitea CLI command failed." string where the other hosts surface the hint. Smallest fix is to include gitea in the alternation:

- /^(github|gitlab|bitbucket|azure devops)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,+ /^(github|gitlab|bitbucket|azure devops|gitea)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,

Minor, optional: the "Add project" command item's searchTerms (apps/web/src/components/CommandPalette.tsx:1547) lists github/gitlab/bitbucket/azure/devops but not gitea, so typing "gitea" no longer reaches the flow that now offers a Gitea source.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a large, cross-cutting Gitea integration with new authenticated repository, pull-request, checkout, and publishing workflows across production server and client paths. A remaining error-classification concern may cause missing pull requests to surface as generic command failures, so the runtime behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[MDragonryu]

Addressed the review findings in :\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout , and required a real NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[MDragonryu]

Addressed the review findings in commit 3e5118d:\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing tea executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout --force, and required a real tea login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Service definition, dependency acquisition (GiteaCli/GiteaSourceControlProvider both acquire their deps with yield* and expose make/layer), namespace imports, and the registry/layer wiring all look consistent with the sibling providers. Two error-modelling points below.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit 3f98c41:\n\n- createPullRequest no longer supplies a PR reference to HTTP error mapping, so a create-time 404 is a GiteaCliCommandError; existing get/checkout PR 404s remain not-found\n- listPullRequests now requests sort=recentupdate, keeping current-branch PR discovery within the bounded page window\n\nThe focused Linux devcontainer suite now passes 8 files and 164 tests.

[MDragonryu]

Follow-up Effect cleanup pushed in commit c0599af:\n\n- removed the redundant single-valued list decode operation field\n- removed the manufactured non-array JSON Error; decoder failures now carry the real schema failure while malformed JSON retains the real parse exception\n\nThe focused Linux devcontainer suite remains green: 8 files, 164 tests.

[macroscopeapp]

One finding: the new tea branch in classifyNonZeroExit changes backend error classification but has no focused test, and no tea rule produces not-found, so GiteaCli.checkoutPullRequest's not-found mapping is unreachable in production. Everything else in the new Gitea service modules follows the conventions (subpath namespace imports, inline Context.Service interface, make acquiring VcsProcess/GiteaCli from the environment, Schema.TaggedErrorClass errors with structural attributes and preserved cause, exported Schema.is predicate, layer at the bottom).

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

This changes backend failure classification (a tea exit mentioning "no available login" now surfaces as GiteaCliAuthenticationError rather than GiteaCliCommandError), but VcsProcess.test.ts has no case for it even though it already covers the analogous authentication and rate-limited phrases. Consider adding a focused case asserting failureKind: "authentication" for command: "tea" with that stderr, plus one asserting another command with the same phrase stays command-failed (the reason the rule is scoped to tea).

Related: no tea branch exists in the not-found block below, so classifyNonZeroExit never returns not-found for tea. GiteaCli.checkoutPullRequest's GiteaPullRequestNotFoundError.fromVcsError path is therefore only reachable in the unit test that hand-builds failureKind: "not-found"; a real tea pulls checkout 9999 failure maps to GiteaCliCommandError. Worth either adding the tea not-found phrases here or dropping the unreachable branch.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit d257b11:\n\n- full PR URL checkout now verifies the URL repository against the current Gitea repository before invoking tea, preserving same-repository and numeric checkout behavior\n- public github.com and bitbucket.org /pulls/ URLs are excluded from the generic Gitea reference parser while self-hosted lookalikes remain supported\n- added regression coverage for the repository guard and URL parsing\n\nVerification: 8 focused Linux devcontainer test files, 168 tests passed; targeted server/web TypeScript checks completed.

[macroscopeapp]

One new finding on the Gitea CLI error model, plus one earlier finding that is still open (see below). Everything else in the Gitea service/provider pair follows the conventions: namespaced effect/* imports, Context.Service with an inline interface, exported make/layer, dependencies acquired via yield* VcsProcess.VcsProcess / yield* GiteaCli.GiteaCli, structured Schema.TaggedErrorClass failures with real causes preserved and messages derived from stable attributes, and Schema.Union + Schema.is for the error predicate.

Still open from a previous run (not re-commented): apps/server/src/vcs/VcsProcess.ts changes non-zero-exit classification so a tea failure mentioning "no available login" is now categorized as authentication, and apps/server/src/vcs/VcsProcess.test.ts still has no case covering it (nor a case proving another command with the same phrase stays command-failed). Backend behavior changes should carry focused tests.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up test/convention fixes pushed in commit 556ce2d:\n\n- removed the redundant single-value Gitea pull-request decode operation field\n- added focused coverage for tea no-available-login authentication classification and the non-tea negative case\n\nVerification: 9 focused Linux devcontainer test files, 182 tests passed.

[macroscopeapp]

Reviewed the changed web UI surfaces for the Gitea provider addition (CommandPalette.tsx, GitActionsControl.tsx, SourceControlSettings.tsx, sourceControlPresentation.ts, pullRequestLinkContextMenu.ts, pullRequestDetail.logic.ts, openPullRequestLink.ts, pullRequestReference.ts). Provider enumerations, labels, icons and readiness maps are consistent, and the reference parser gap flagged on the earlier revision is now closed.

Two findings, one behavioral:

1. openPullRequestLink.ts now claims Gitea /pulls/{n} URLs, which makes those links open the in-app change-request surfaces even though this build registers no Gitea pull-request provider — the reader lands on the "Could not load pull requests" empty state instead of the host page they previously got in the browser.
2. GitActionsControl.tsx uses the literal "gitea" as the publish-dialog host, which is rendered as a hostname prefix when discovery reports no host.

^{Posted via Macroscope — UI Consistency}

[MDragonryu]

Final review cycle for 556ce2d is complete. Cursor Bugbot, Macroscope Correctness, Effect Service Conventions, and UI Consistency are green; the Approvability check completed neutral with correctness checked and eligibility unchecked. No new inline comments were posted on the current head. The worktree is clean and the PR is ready for human review.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16d32bc. Configure here.}

[macroscopeapp]

Two findings, both in the Source Control settings copy that this PR reworked to make room for Gitea's tea login add hint. The rest of the Gitea UI wiring (neutral GitPullRequestIcon for the unbranded provider, resolvePublishHost host fallback, /pulls/ link handling) looks consistent with the existing provider patterns.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

login add is a tea-only subcommand, but this helper renders the unauthenticated row for every provider, so GitHub now reads "Run gh login add", GitLab "Run glab login add" and Azure DevOps "Run az login add" — none of those commands exist (gh auth login, glab auth login, az login). The copy that was replaced was deliberately executable-agnostic.

Consider keeping the neutral phrasing here (or threading a per-provider auth command through the discovery spec) so only Gitea gets the tea login add wording:

Suggested change

	if(executable!==null){
	return`${label} is not authenticated on this server. Run \`${executable} login add\` on the server host to enable change request features.`;
	return`${label} is not authenticated on this server. Sign in or configure credentials using the \`${executable}\` tool on the server host to enable change request features.`;

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

We do not have a current support commitment for Gitea. This 39-file branch would add a source control CLI, discovery, repository operations, settings, contracts, icons, and a permanent compatibility obligation.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[MDragonryu]

Summary

• add Gitea discovery and authentication through tea
• implement repository, branch, pull-request, and provider operations
• wire Gitea through server, web, mobile, contracts, Git actions, and documentation
• add focused coverage for CLI parsing, provider behavior, registry discovery, and source-control contracts

Testing

• CI=true pnpm exec vp test run apps/server/src/sourceControl/GiteaCli.test.ts apps/server/src/sourceControl/GiteaSourceControlProvider.test.ts apps/server/src/sourceControl/giteaLogins.test.ts apps/server/src/sourceControl/SourceControlProviderRegistry.test.ts packages/shared/src/sourceControl.test.ts packages/contracts/src/sourceControl.test.ts
• 6 test files passed, 109 tests passed
• live validation completed against a fresh Gitea container with repository, commit/push, and three pull-request scenarios

Notes

Gitea support uses the authenticated tea CLI and preserves the existing provider architecture across server and clients.

---

Note

Medium Risk
Changes git stacked actions, PR creation/deduping, and remote provider resolution; behavior is heavily tested but errors could still mis-route remotes or mishandle tea HTTP responses.

Overview
Adds first-class Gitea support end-to-end so remotes no longer resolve to unknown and Commit, push & create PR works against Gitea hosts.

On the server, a new GiteaCli layer wraps the tea tool (API calls with HTTP status parsing because tea api exits 0 on errors, client-side PR list filtering/pagination, repo publish routing to user/repos vs orgs/.../repos). GiteaSourceControlProvider plugs into the existing registry with CLI discovery from tea logins list and host-based refinement of otherwise-unknown self-hosted remotes when tea is logged into that host.

Contracts, shared remote detection (gitea.com / *gitea* hosts), web and mobile add-project/publish/settings flows, and docs are extended for gitea. Publish UI uses discovery for hostname when there is no canonical host. In-app deep links still skip Gitea (parseChangeRequestUrl does not claim /pulls/{n}), while checkout/reference parsing accepts Gitea URLs and tea pulls checkout.

VcsProcess now treats tea’s “no available login” stderr as an authentication failure.

^{Reviewed by Cursor Bugbot for commit d1b9069. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Gitea source-control provider across backend, web, and mobile

• Implements GiteaCli wrapper around the tea CLI in GiteaCli.ts, covering PR list/get/create, repo creation, clone URLs, default branch, and checkout, with typed errors and HTTP status mapping.
• Adds GiteaSourceControlProvider in GiteaSourceControlProvider.ts implementing the provider contract, plus discovery and auth parsing based on tea logins list output.
• Wires Gitea into the server provider registry and WebSocket RPC layers in server.ts and ws.ts.
• Updates web, mobile, and shared packages: command palette, publish dialog, PR reference parsing, settings UI, icons, and provider detection.
• Risk: new 'gitea' literal added to SourceControlProviderKind schema in sourceControl.ts; out-of-tree contract consumers must regenerate schemas to decode the new kind.

^{Macroscope summarized d1b9069.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e4dce5a6-b2ec-4eb6-81ff-3ae86dc8f69e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Structure, namespace imports, Context.Service + inline interface, make/layer, and environment-based dependency acquisition all look right, and the test-only service-instance injection in GitManager.test.ts is a legitimate seam. Three findings on error modeling in apps/server/src/sourceControl/GiteaCli.ts.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI Consistency: 2 findings

Provider plumbing for the web client is otherwise complete and consistent (icon maps, labels, path hints, readiness, publish host, "Open on Gitea"). Two web surfaces that key off provider identity were not extended with the new kind, so Gitea users get different behaviour from every other host:

1. apps/web/src/lib/openPullRequestLink.ts (inline comment) — Gitea PR URLs are now readable for opening links, but apps/web/src/pullRequestReference.ts still rejects them for input, while the input placeholder promises "PR URL, checkout command, or #42".

2. apps/web/src/components/pullRequest/pullRequestDetail.logic.ts:855 — TOOL_NOISE replaces content-free host errors with an actionable hint for github|gitlab|bitbucket|azure devops, but the new provider's GiteaCliCommandError.detail is "Gitea CLI command failed." (apps/server/src/sourceControl/GiteaCli.ts:121), which no pattern matches. A failed Gitea action therefore surfaces the bare "Gitea CLI command failed." string where the other hosts surface the hint. Smallest fix is to include gitea in the alternation:

- /^(github|gitlab|bitbucket|azure devops)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,+ /^(github|gitlab|bitbucket|azure devops|gitea)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,

Minor, optional: the "Add project" command item's searchTerms (apps/web/src/components/CommandPalette.tsx:1547) lists github/gitlab/bitbucket/azure/devops but not gitea, so typing "gitea" no longer reaches the flow that now offers a Gitea source.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a large, cross-cutting Gitea integration with new authenticated repository, pull-request, checkout, and publishing workflows across production server and client paths. A remaining error-classification concern may cause missing pull requests to surface as generic command failures, so the runtime behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[MDragonryu]

Addressed the review findings in :\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout , and required a real NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[MDragonryu]

Addressed the review findings in commit 3e5118d:\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing tea executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout --force, and required a real tea login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Service definition, dependency acquisition (GiteaCli/GiteaSourceControlProvider both acquire their deps with yield* and expose make/layer), namespace imports, and the registry/layer wiring all look consistent with the sibling providers. Two error-modelling points below.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit 3f98c41:\n\n- createPullRequest no longer supplies a PR reference to HTTP error mapping, so a create-time 404 is a GiteaCliCommandError; existing get/checkout PR 404s remain not-found\n- listPullRequests now requests sort=recentupdate, keeping current-branch PR discovery within the bounded page window\n\nThe focused Linux devcontainer suite now passes 8 files and 164 tests.

[MDragonryu]

Follow-up Effect cleanup pushed in commit c0599af:\n\n- removed the redundant single-valued list decode operation field\n- removed the manufactured non-array JSON Error; decoder failures now carry the real schema failure while malformed JSON retains the real parse exception\n\nThe focused Linux devcontainer suite remains green: 8 files, 164 tests.

[macroscopeapp]

One finding: the new tea branch in classifyNonZeroExit changes backend error classification but has no focused test, and no tea rule produces not-found, so GiteaCli.checkoutPullRequest's not-found mapping is unreachable in production. Everything else in the new Gitea service modules follows the conventions (subpath namespace imports, inline Context.Service interface, make acquiring VcsProcess/GiteaCli from the environment, Schema.TaggedErrorClass errors with structural attributes and preserved cause, exported Schema.is predicate, layer at the bottom).

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

This changes backend failure classification (a tea exit mentioning "no available login" now surfaces as GiteaCliAuthenticationError rather than GiteaCliCommandError), but VcsProcess.test.ts has no case for it even though it already covers the analogous authentication and rate-limited phrases. Consider adding a focused case asserting failureKind: "authentication" for command: "tea" with that stderr, plus one asserting another command with the same phrase stays command-failed (the reason the rule is scoped to tea).

Related: no tea branch exists in the not-found block below, so classifyNonZeroExit never returns not-found for tea. GiteaCli.checkoutPullRequest's GiteaPullRequestNotFoundError.fromVcsError path is therefore only reachable in the unit test that hand-builds failureKind: "not-found"; a real tea pulls checkout 9999 failure maps to GiteaCliCommandError. Worth either adding the tea not-found phrases here or dropping the unreachable branch.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit d257b11:\n\n- full PR URL checkout now verifies the URL repository against the current Gitea repository before invoking tea, preserving same-repository and numeric checkout behavior\n- public github.com and bitbucket.org /pulls/ URLs are excluded from the generic Gitea reference parser while self-hosted lookalikes remain supported\n- added regression coverage for the repository guard and URL parsing\n\nVerification: 8 focused Linux devcontainer test files, 168 tests passed; targeted server/web TypeScript checks completed.

[macroscopeapp]

One new finding on the Gitea CLI error model, plus one earlier finding that is still open (see below). Everything else in the Gitea service/provider pair follows the conventions: namespaced effect/* imports, Context.Service with an inline interface, exported make/layer, dependencies acquired via yield* VcsProcess.VcsProcess / yield* GiteaCli.GiteaCli, structured Schema.TaggedErrorClass failures with real causes preserved and messages derived from stable attributes, and Schema.Union + Schema.is for the error predicate.

Still open from a previous run (not re-commented): apps/server/src/vcs/VcsProcess.ts changes non-zero-exit classification so a tea failure mentioning "no available login" is now categorized as authentication, and apps/server/src/vcs/VcsProcess.test.ts still has no case covering it (nor a case proving another command with the same phrase stays command-failed). Backend behavior changes should carry focused tests.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up test/convention fixes pushed in commit 556ce2d:\n\n- removed the redundant single-value Gitea pull-request decode operation field\n- added focused coverage for tea no-available-login authentication classification and the non-tea negative case\n\nVerification: 9 focused Linux devcontainer test files, 182 tests passed.

[macroscopeapp]

Reviewed the changed web UI surfaces for the Gitea provider addition (CommandPalette.tsx, GitActionsControl.tsx, SourceControlSettings.tsx, sourceControlPresentation.ts, pullRequestLinkContextMenu.ts, pullRequestDetail.logic.ts, openPullRequestLink.ts, pullRequestReference.ts). Provider enumerations, labels, icons and readiness maps are consistent, and the reference parser gap flagged on the earlier revision is now closed.

Two findings, one behavioral:

1. openPullRequestLink.ts now claims Gitea /pulls/{n} URLs, which makes those links open the in-app change-request surfaces even though this build registers no Gitea pull-request provider — the reader lands on the "Could not load pull requests" empty state instead of the host page they previously got in the browser.
2. GitActionsControl.tsx uses the literal "gitea" as the publish-dialog host, which is rendered as a hostname prefix when discovery reports no host.

^{Posted via Macroscope — UI Consistency}

[MDragonryu]

Final review cycle for 556ce2d is complete. Cursor Bugbot, Macroscope Correctness, Effect Service Conventions, and UI Consistency are green; the Approvability check completed neutral with correctness checked and eligibility unchecked. No new inline comments were posted on the current head. The worktree is clean and the PR is ready for human review.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16d32bc. Configure here.}

[macroscopeapp]

Two findings, both in the Source Control settings copy that this PR reworked to make room for Gitea's tea login add hint. The rest of the Gitea UI wiring (neutral GitPullRequestIcon for the unbranded provider, resolvePublishHost host fallback, /pulls/ link handling) looks consistent with the existing provider patterns.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

login add is a tea-only subcommand, but this helper renders the unauthenticated row for every provider, so GitHub now reads "Run gh login add", GitLab "Run glab login add" and Azure DevOps "Run az login add" — none of those commands exist (gh auth login, glab auth login, az login). The copy that was replaced was deliberately executable-agnostic.

Consider keeping the neutral phrasing here (or threading a per-provider auth command through the discovery spec) so only Gitea gets the tea login add wording:

Suggested change

	if(executable!==null){
	return`${label} is not authenticated on this server. Run \`${executable} login add\` on the server host to enable change request features.`;
	return`${label} is not authenticated on this server. Sign in or configure credentials using the \`${executable}\` tool on the server host to enable change request features.`;

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

We do not have a current support commitment for Gitea. This 39-file branch would add a source control CLI, discovery, repository operations, settings, contracts, icons, and a permanent compatibility obligation.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[MDragonryu]

Summary

• add Gitea discovery and authentication through tea
• implement repository, branch, pull-request, and provider operations
• wire Gitea through server, web, mobile, contracts, Git actions, and documentation
• add focused coverage for CLI parsing, provider behavior, registry discovery, and source-control contracts

Testing

• CI=true pnpm exec vp test run apps/server/src/sourceControl/GiteaCli.test.ts apps/server/src/sourceControl/GiteaSourceControlProvider.test.ts apps/server/src/sourceControl/giteaLogins.test.ts apps/server/src/sourceControl/SourceControlProviderRegistry.test.ts packages/shared/src/sourceControl.test.ts packages/contracts/src/sourceControl.test.ts
• 6 test files passed, 109 tests passed
• live validation completed against a fresh Gitea container with repository, commit/push, and three pull-request scenarios

Notes

Gitea support uses the authenticated tea CLI and preserves the existing provider architecture across server and clients.

---

Note

Medium Risk
Changes git stacked actions, PR creation/deduping, and remote provider resolution; behavior is heavily tested but errors could still mis-route remotes or mishandle tea HTTP responses.

Overview
Adds first-class Gitea support end-to-end so remotes no longer resolve to unknown and Commit, push & create PR works against Gitea hosts.

On the server, a new GiteaCli layer wraps the tea tool (API calls with HTTP status parsing because tea api exits 0 on errors, client-side PR list filtering/pagination, repo publish routing to user/repos vs orgs/.../repos). GiteaSourceControlProvider plugs into the existing registry with CLI discovery from tea logins list and host-based refinement of otherwise-unknown self-hosted remotes when tea is logged into that host.

Contracts, shared remote detection (gitea.com / *gitea* hosts), web and mobile add-project/publish/settings flows, and docs are extended for gitea. Publish UI uses discovery for hostname when there is no canonical host. In-app deep links still skip Gitea (parseChangeRequestUrl does not claim /pulls/{n}), while checkout/reference parsing accepts Gitea URLs and tea pulls checkout.

VcsProcess now treats tea’s “no available login” stderr as an authentication failure.

^{Reviewed by Cursor Bugbot for commit d1b9069. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Gitea source-control provider across backend, web, and mobile

• Implements GiteaCli wrapper around the tea CLI in GiteaCli.ts, covering PR list/get/create, repo creation, clone URLs, default branch, and checkout, with typed errors and HTTP status mapping.
• Adds GiteaSourceControlProvider in GiteaSourceControlProvider.ts implementing the provider contract, plus discovery and auth parsing based on tea logins list output.
• Wires Gitea into the server provider registry and WebSocket RPC layers in server.ts and ws.ts.
• Updates web, mobile, and shared packages: command palette, publish dialog, PR reference parsing, settings UI, icons, and provider detection.
• Risk: new 'gitea' literal added to SourceControlProviderKind schema in sourceControl.ts; out-of-tree contract consumers must regenerate schemas to decode the new kind.

^{Macroscope summarized d1b9069.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e4dce5a6-b2ec-4eb6-81ff-3ae86dc8f69e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Structure, namespace imports, Context.Service + inline interface, make/layer, and environment-based dependency acquisition all look right, and the test-only service-instance injection in GitManager.test.ts is a legitimate seam. Three findings on error modeling in apps/server/src/sourceControl/GiteaCli.ts.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI Consistency: 2 findings

Provider plumbing for the web client is otherwise complete and consistent (icon maps, labels, path hints, readiness, publish host, "Open on Gitea"). Two web surfaces that key off provider identity were not extended with the new kind, so Gitea users get different behaviour from every other host:

1. apps/web/src/lib/openPullRequestLink.ts (inline comment) — Gitea PR URLs are now readable for opening links, but apps/web/src/pullRequestReference.ts still rejects them for input, while the input placeholder promises "PR URL, checkout command, or #42".

2. apps/web/src/components/pullRequest/pullRequestDetail.logic.ts:855 — TOOL_NOISE replaces content-free host errors with an actionable hint for github|gitlab|bitbucket|azure devops, but the new provider's GiteaCliCommandError.detail is "Gitea CLI command failed." (apps/server/src/sourceControl/GiteaCli.ts:121), which no pattern matches. A failed Gitea action therefore surfaces the bare "Gitea CLI command failed." string where the other hosts surface the hint. Smallest fix is to include gitea in the alternation:

- /^(github|gitlab|bitbucket|azure devops)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,+ /^(github|gitlab|bitbucket|azure devops|gitea)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,

Minor, optional: the "Add project" command item's searchTerms (apps/web/src/components/CommandPalette.tsx:1547) lists github/gitlab/bitbucket/azure/devops but not gitea, so typing "gitea" no longer reaches the flow that now offers a Gitea source.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a large, cross-cutting Gitea integration with new authenticated repository, pull-request, checkout, and publishing workflows across production server and client paths. A remaining error-classification concern may cause missing pull requests to surface as generic command failures, so the runtime behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[MDragonryu]

Addressed the review findings in :\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout , and required a real NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[MDragonryu]

Addressed the review findings in commit 3e5118d:\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing tea executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout --force, and required a real tea login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Service definition, dependency acquisition (GiteaCli/GiteaSourceControlProvider both acquire their deps with yield* and expose make/layer), namespace imports, and the registry/layer wiring all look consistent with the sibling providers. Two error-modelling points below.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit 3f98c41:\n\n- createPullRequest no longer supplies a PR reference to HTTP error mapping, so a create-time 404 is a GiteaCliCommandError; existing get/checkout PR 404s remain not-found\n- listPullRequests now requests sort=recentupdate, keeping current-branch PR discovery within the bounded page window\n\nThe focused Linux devcontainer suite now passes 8 files and 164 tests.

[MDragonryu]

Follow-up Effect cleanup pushed in commit c0599af:\n\n- removed the redundant single-valued list decode operation field\n- removed the manufactured non-array JSON Error; decoder failures now carry the real schema failure while malformed JSON retains the real parse exception\n\nThe focused Linux devcontainer suite remains green: 8 files, 164 tests.

[macroscopeapp]

One finding: the new tea branch in classifyNonZeroExit changes backend error classification but has no focused test, and no tea rule produces not-found, so GiteaCli.checkoutPullRequest's not-found mapping is unreachable in production. Everything else in the new Gitea service modules follows the conventions (subpath namespace imports, inline Context.Service interface, make acquiring VcsProcess/GiteaCli from the environment, Schema.TaggedErrorClass errors with structural attributes and preserved cause, exported Schema.is predicate, layer at the bottom).

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

This changes backend failure classification (a tea exit mentioning "no available login" now surfaces as GiteaCliAuthenticationError rather than GiteaCliCommandError), but VcsProcess.test.ts has no case for it even though it already covers the analogous authentication and rate-limited phrases. Consider adding a focused case asserting failureKind: "authentication" for command: "tea" with that stderr, plus one asserting another command with the same phrase stays command-failed (the reason the rule is scoped to tea).

Related: no tea branch exists in the not-found block below, so classifyNonZeroExit never returns not-found for tea. GiteaCli.checkoutPullRequest's GiteaPullRequestNotFoundError.fromVcsError path is therefore only reachable in the unit test that hand-builds failureKind: "not-found"; a real tea pulls checkout 9999 failure maps to GiteaCliCommandError. Worth either adding the tea not-found phrases here or dropping the unreachable branch.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit d257b11:\n\n- full PR URL checkout now verifies the URL repository against the current Gitea repository before invoking tea, preserving same-repository and numeric checkout behavior\n- public github.com and bitbucket.org /pulls/ URLs are excluded from the generic Gitea reference parser while self-hosted lookalikes remain supported\n- added regression coverage for the repository guard and URL parsing\n\nVerification: 8 focused Linux devcontainer test files, 168 tests passed; targeted server/web TypeScript checks completed.

[macroscopeapp]

One new finding on the Gitea CLI error model, plus one earlier finding that is still open (see below). Everything else in the Gitea service/provider pair follows the conventions: namespaced effect/* imports, Context.Service with an inline interface, exported make/layer, dependencies acquired via yield* VcsProcess.VcsProcess / yield* GiteaCli.GiteaCli, structured Schema.TaggedErrorClass failures with real causes preserved and messages derived from stable attributes, and Schema.Union + Schema.is for the error predicate.

Still open from a previous run (not re-commented): apps/server/src/vcs/VcsProcess.ts changes non-zero-exit classification so a tea failure mentioning "no available login" is now categorized as authentication, and apps/server/src/vcs/VcsProcess.test.ts still has no case covering it (nor a case proving another command with the same phrase stays command-failed). Backend behavior changes should carry focused tests.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up test/convention fixes pushed in commit 556ce2d:\n\n- removed the redundant single-value Gitea pull-request decode operation field\n- added focused coverage for tea no-available-login authentication classification and the non-tea negative case\n\nVerification: 9 focused Linux devcontainer test files, 182 tests passed.

[macroscopeapp]

Reviewed the changed web UI surfaces for the Gitea provider addition (CommandPalette.tsx, GitActionsControl.tsx, SourceControlSettings.tsx, sourceControlPresentation.ts, pullRequestLinkContextMenu.ts, pullRequestDetail.logic.ts, openPullRequestLink.ts, pullRequestReference.ts). Provider enumerations, labels, icons and readiness maps are consistent, and the reference parser gap flagged on the earlier revision is now closed.

Two findings, one behavioral:

1. openPullRequestLink.ts now claims Gitea /pulls/{n} URLs, which makes those links open the in-app change-request surfaces even though this build registers no Gitea pull-request provider — the reader lands on the "Could not load pull requests" empty state instead of the host page they previously got in the browser.
2. GitActionsControl.tsx uses the literal "gitea" as the publish-dialog host, which is rendered as a hostname prefix when discovery reports no host.

^{Posted via Macroscope — UI Consistency}

[MDragonryu]

Final review cycle for 556ce2d is complete. Cursor Bugbot, Macroscope Correctness, Effect Service Conventions, and UI Consistency are green; the Approvability check completed neutral with correctness checked and eligibility unchecked. No new inline comments were posted on the current head. The worktree is clean and the PR is ready for human review.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16d32bc. Configure here.}

[macroscopeapp]

Two findings, both in the Source Control settings copy that this PR reworked to make room for Gitea's tea login add hint. The rest of the Gitea UI wiring (neutral GitPullRequestIcon for the unbranded provider, resolvePublishHost host fallback, /pulls/ link handling) looks consistent with the existing provider patterns.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

login add is a tea-only subcommand, but this helper renders the unauthenticated row for every provider, so GitHub now reads "Run gh login add", GitLab "Run glab login add" and Azure DevOps "Run az login add" — none of those commands exist (gh auth login, glab auth login, az login). The copy that was replaced was deliberately executable-agnostic.

Consider keeping the neutral phrasing here (or threading a per-provider auth command through the discovery spec) so only Gitea gets the tea login add wording:

Suggested change

	if(executable!==null){
	return`${label} is not authenticated on this server. Run \`${executable} login add\` on the server host to enable change request features.`;
	return`${label} is not authenticated on this server. Sign in or configure credentials using the \`${executable}\` tool on the server host to enable change request features.`;

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

We do not have a current support commitment for Gitea. This 39-file branch would add a source control CLI, discovery, repository operations, settings, contracts, icons, and a permanent compatibility obligation.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[MDragonryu]

Summary

• add Gitea discovery and authentication through tea
• implement repository, branch, pull-request, and provider operations
• wire Gitea through server, web, mobile, contracts, Git actions, and documentation
• add focused coverage for CLI parsing, provider behavior, registry discovery, and source-control contracts

Testing

• CI=true pnpm exec vp test run apps/server/src/sourceControl/GiteaCli.test.ts apps/server/src/sourceControl/GiteaSourceControlProvider.test.ts apps/server/src/sourceControl/giteaLogins.test.ts apps/server/src/sourceControl/SourceControlProviderRegistry.test.ts packages/shared/src/sourceControl.test.ts packages/contracts/src/sourceControl.test.ts
• 6 test files passed, 109 tests passed
• live validation completed against a fresh Gitea container with repository, commit/push, and three pull-request scenarios

Notes

Gitea support uses the authenticated tea CLI and preserves the existing provider architecture across server and clients.

---

Note

Medium Risk
Changes git stacked actions, PR creation/deduping, and remote provider resolution; behavior is heavily tested but errors could still mis-route remotes or mishandle tea HTTP responses.

Overview
Adds first-class Gitea support end-to-end so remotes no longer resolve to unknown and Commit, push & create PR works against Gitea hosts.

On the server, a new GiteaCli layer wraps the tea tool (API calls with HTTP status parsing because tea api exits 0 on errors, client-side PR list filtering/pagination, repo publish routing to user/repos vs orgs/.../repos). GiteaSourceControlProvider plugs into the existing registry with CLI discovery from tea logins list and host-based refinement of otherwise-unknown self-hosted remotes when tea is logged into that host.

Contracts, shared remote detection (gitea.com / *gitea* hosts), web and mobile add-project/publish/settings flows, and docs are extended for gitea. Publish UI uses discovery for hostname when there is no canonical host. In-app deep links still skip Gitea (parseChangeRequestUrl does not claim /pulls/{n}), while checkout/reference parsing accepts Gitea URLs and tea pulls checkout.

VcsProcess now treats tea’s “no available login” stderr as an authentication failure.

^{Reviewed by Cursor Bugbot for commit d1b9069. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Gitea source-control provider across backend, web, and mobile

• Implements GiteaCli wrapper around the tea CLI in GiteaCli.ts, covering PR list/get/create, repo creation, clone URLs, default branch, and checkout, with typed errors and HTTP status mapping.
• Adds GiteaSourceControlProvider in GiteaSourceControlProvider.ts implementing the provider contract, plus discovery and auth parsing based on tea logins list output.
• Wires Gitea into the server provider registry and WebSocket RPC layers in server.ts and ws.ts.
• Updates web, mobile, and shared packages: command palette, publish dialog, PR reference parsing, settings UI, icons, and provider detection.
• Risk: new 'gitea' literal added to SourceControlProviderKind schema in sourceControl.ts; out-of-tree contract consumers must regenerate schemas to decode the new kind.

^{Macroscope summarized d1b9069.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e4dce5a6-b2ec-4eb6-81ff-3ae86dc8f69e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Structure, namespace imports, Context.Service + inline interface, make/layer, and environment-based dependency acquisition all look right, and the test-only service-instance injection in GitManager.test.ts is a legitimate seam. Three findings on error modeling in apps/server/src/sourceControl/GiteaCli.ts.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI Consistency: 2 findings

Provider plumbing for the web client is otherwise complete and consistent (icon maps, labels, path hints, readiness, publish host, "Open on Gitea"). Two web surfaces that key off provider identity were not extended with the new kind, so Gitea users get different behaviour from every other host:

1. apps/web/src/lib/openPullRequestLink.ts (inline comment) — Gitea PR URLs are now readable for opening links, but apps/web/src/pullRequestReference.ts still rejects them for input, while the input placeholder promises "PR URL, checkout command, or #42".

2. apps/web/src/components/pullRequest/pullRequestDetail.logic.ts:855 — TOOL_NOISE replaces content-free host errors with an actionable hint for github|gitlab|bitbucket|azure devops, but the new provider's GiteaCliCommandError.detail is "Gitea CLI command failed." (apps/server/src/sourceControl/GiteaCli.ts:121), which no pattern matches. A failed Gitea action therefore surfaces the bare "Gitea CLI command failed." string where the other hosts surface the hint. Smallest fix is to include gitea in the alternation:

- /^(github|gitlab|bitbucket|azure devops)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,+ /^(github|gitlab|bitbucket|azure devops|gitea)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,

Minor, optional: the "Add project" command item's searchTerms (apps/web/src/components/CommandPalette.tsx:1547) lists github/gitlab/bitbucket/azure/devops but not gitea, so typing "gitea" no longer reaches the flow that now offers a Gitea source.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a large, cross-cutting Gitea integration with new authenticated repository, pull-request, checkout, and publishing workflows across production server and client paths. A remaining error-classification concern may cause missing pull requests to surface as generic command failures, so the runtime behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[MDragonryu]

Addressed the review findings in :\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout , and required a real NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[MDragonryu]

Addressed the review findings in commit 3e5118d:\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing tea executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout --force, and required a real tea login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Service definition, dependency acquisition (GiteaCli/GiteaSourceControlProvider both acquire their deps with yield* and expose make/layer), namespace imports, and the registry/layer wiring all look consistent with the sibling providers. Two error-modelling points below.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit 3f98c41:\n\n- createPullRequest no longer supplies a PR reference to HTTP error mapping, so a create-time 404 is a GiteaCliCommandError; existing get/checkout PR 404s remain not-found\n- listPullRequests now requests sort=recentupdate, keeping current-branch PR discovery within the bounded page window\n\nThe focused Linux devcontainer suite now passes 8 files and 164 tests.

[MDragonryu]

Follow-up Effect cleanup pushed in commit c0599af:\n\n- removed the redundant single-valued list decode operation field\n- removed the manufactured non-array JSON Error; decoder failures now carry the real schema failure while malformed JSON retains the real parse exception\n\nThe focused Linux devcontainer suite remains green: 8 files, 164 tests.

[macroscopeapp]

One finding: the new tea branch in classifyNonZeroExit changes backend error classification but has no focused test, and no tea rule produces not-found, so GiteaCli.checkoutPullRequest's not-found mapping is unreachable in production. Everything else in the new Gitea service modules follows the conventions (subpath namespace imports, inline Context.Service interface, make acquiring VcsProcess/GiteaCli from the environment, Schema.TaggedErrorClass errors with structural attributes and preserved cause, exported Schema.is predicate, layer at the bottom).

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

This changes backend failure classification (a tea exit mentioning "no available login" now surfaces as GiteaCliAuthenticationError rather than GiteaCliCommandError), but VcsProcess.test.ts has no case for it even though it already covers the analogous authentication and rate-limited phrases. Consider adding a focused case asserting failureKind: "authentication" for command: "tea" with that stderr, plus one asserting another command with the same phrase stays command-failed (the reason the rule is scoped to tea).

Related: no tea branch exists in the not-found block below, so classifyNonZeroExit never returns not-found for tea. GiteaCli.checkoutPullRequest's GiteaPullRequestNotFoundError.fromVcsError path is therefore only reachable in the unit test that hand-builds failureKind: "not-found"; a real tea pulls checkout 9999 failure maps to GiteaCliCommandError. Worth either adding the tea not-found phrases here or dropping the unreachable branch.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit d257b11:\n\n- full PR URL checkout now verifies the URL repository against the current Gitea repository before invoking tea, preserving same-repository and numeric checkout behavior\n- public github.com and bitbucket.org /pulls/ URLs are excluded from the generic Gitea reference parser while self-hosted lookalikes remain supported\n- added regression coverage for the repository guard and URL parsing\n\nVerification: 8 focused Linux devcontainer test files, 168 tests passed; targeted server/web TypeScript checks completed.

[macroscopeapp]

One new finding on the Gitea CLI error model, plus one earlier finding that is still open (see below). Everything else in the Gitea service/provider pair follows the conventions: namespaced effect/* imports, Context.Service with an inline interface, exported make/layer, dependencies acquired via yield* VcsProcess.VcsProcess / yield* GiteaCli.GiteaCli, structured Schema.TaggedErrorClass failures with real causes preserved and messages derived from stable attributes, and Schema.Union + Schema.is for the error predicate.

Still open from a previous run (not re-commented): apps/server/src/vcs/VcsProcess.ts changes non-zero-exit classification so a tea failure mentioning "no available login" is now categorized as authentication, and apps/server/src/vcs/VcsProcess.test.ts still has no case covering it (nor a case proving another command with the same phrase stays command-failed). Backend behavior changes should carry focused tests.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up test/convention fixes pushed in commit 556ce2d:\n\n- removed the redundant single-value Gitea pull-request decode operation field\n- added focused coverage for tea no-available-login authentication classification and the non-tea negative case\n\nVerification: 9 focused Linux devcontainer test files, 182 tests passed.

[macroscopeapp]

Reviewed the changed web UI surfaces for the Gitea provider addition (CommandPalette.tsx, GitActionsControl.tsx, SourceControlSettings.tsx, sourceControlPresentation.ts, pullRequestLinkContextMenu.ts, pullRequestDetail.logic.ts, openPullRequestLink.ts, pullRequestReference.ts). Provider enumerations, labels, icons and readiness maps are consistent, and the reference parser gap flagged on the earlier revision is now closed.

Two findings, one behavioral:

1. openPullRequestLink.ts now claims Gitea /pulls/{n} URLs, which makes those links open the in-app change-request surfaces even though this build registers no Gitea pull-request provider — the reader lands on the "Could not load pull requests" empty state instead of the host page they previously got in the browser.
2. GitActionsControl.tsx uses the literal "gitea" as the publish-dialog host, which is rendered as a hostname prefix when discovery reports no host.

^{Posted via Macroscope — UI Consistency}

[MDragonryu]

Final review cycle for 556ce2d is complete. Cursor Bugbot, Macroscope Correctness, Effect Service Conventions, and UI Consistency are green; the Approvability check completed neutral with correctness checked and eligibility unchecked. No new inline comments were posted on the current head. The worktree is clean and the PR is ready for human review.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16d32bc. Configure here.}

[macroscopeapp]

Two findings, both in the Source Control settings copy that this PR reworked to make room for Gitea's tea login add hint. The rest of the Gitea UI wiring (neutral GitPullRequestIcon for the unbranded provider, resolvePublishHost host fallback, /pulls/ link handling) looks consistent with the existing provider patterns.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

login add is a tea-only subcommand, but this helper renders the unauthenticated row for every provider, so GitHub now reads "Run gh login add", GitLab "Run glab login add" and Azure DevOps "Run az login add" — none of those commands exist (gh auth login, glab auth login, az login). The copy that was replaced was deliberately executable-agnostic.

Consider keeping the neutral phrasing here (or threading a per-provider auth command through the discovery spec) so only Gitea gets the tea login add wording:

Suggested change

	if(executable!==null){
	return`${label} is not authenticated on this server. Run \`${executable} login add\` on the server host to enable change request features.`;
	return`${label} is not authenticated on this server. Sign in or configure credentials using the \`${executable}\` tool on the server host to enable change request features.`;

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

We do not have a current support commitment for Gitea. This 39-file branch would add a source control CLI, discovery, repository operations, settings, contracts, icons, and a permanent compatibility obligation.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[MDragonryu]

Summary

• add Gitea discovery and authentication through tea
• implement repository, branch, pull-request, and provider operations
• wire Gitea through server, web, mobile, contracts, Git actions, and documentation
• add focused coverage for CLI parsing, provider behavior, registry discovery, and source-control contracts

Testing

• CI=true pnpm exec vp test run apps/server/src/sourceControl/GiteaCli.test.ts apps/server/src/sourceControl/GiteaSourceControlProvider.test.ts apps/server/src/sourceControl/giteaLogins.test.ts apps/server/src/sourceControl/SourceControlProviderRegistry.test.ts packages/shared/src/sourceControl.test.ts packages/contracts/src/sourceControl.test.ts
• 6 test files passed, 109 tests passed
• live validation completed against a fresh Gitea container with repository, commit/push, and three pull-request scenarios

Notes

Gitea support uses the authenticated tea CLI and preserves the existing provider architecture across server and clients.

---

Note

Medium Risk
Changes git stacked actions, PR creation/deduping, and remote provider resolution; behavior is heavily tested but errors could still mis-route remotes or mishandle tea HTTP responses.

Overview
Adds first-class Gitea support end-to-end so remotes no longer resolve to unknown and Commit, push & create PR works against Gitea hosts.

On the server, a new GiteaCli layer wraps the tea tool (API calls with HTTP status parsing because tea api exits 0 on errors, client-side PR list filtering/pagination, repo publish routing to user/repos vs orgs/.../repos). GiteaSourceControlProvider plugs into the existing registry with CLI discovery from tea logins list and host-based refinement of otherwise-unknown self-hosted remotes when tea is logged into that host.

Contracts, shared remote detection (gitea.com / *gitea* hosts), web and mobile add-project/publish/settings flows, and docs are extended for gitea. Publish UI uses discovery for hostname when there is no canonical host. In-app deep links still skip Gitea (parseChangeRequestUrl does not claim /pulls/{n}), while checkout/reference parsing accepts Gitea URLs and tea pulls checkout.

VcsProcess now treats tea’s “no available login” stderr as an authentication failure.

^{Reviewed by Cursor Bugbot for commit d1b9069. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Gitea source-control provider across backend, web, and mobile

• Implements GiteaCli wrapper around the tea CLI in GiteaCli.ts, covering PR list/get/create, repo creation, clone URLs, default branch, and checkout, with typed errors and HTTP status mapping.
• Adds GiteaSourceControlProvider in GiteaSourceControlProvider.ts implementing the provider contract, plus discovery and auth parsing based on tea logins list output.
• Wires Gitea into the server provider registry and WebSocket RPC layers in server.ts and ws.ts.
• Updates web, mobile, and shared packages: command palette, publish dialog, PR reference parsing, settings UI, icons, and provider detection.
• Risk: new 'gitea' literal added to SourceControlProviderKind schema in sourceControl.ts; out-of-tree contract consumers must regenerate schemas to decode the new kind.

^{Macroscope summarized d1b9069.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e4dce5a6-b2ec-4eb6-81ff-3ae86dc8f69e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Structure, namespace imports, Context.Service + inline interface, make/layer, and environment-based dependency acquisition all look right, and the test-only service-instance injection in GitManager.test.ts is a legitimate seam. Three findings on error modeling in apps/server/src/sourceControl/GiteaCli.ts.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI Consistency: 2 findings

Provider plumbing for the web client is otherwise complete and consistent (icon maps, labels, path hints, readiness, publish host, "Open on Gitea"). Two web surfaces that key off provider identity were not extended with the new kind, so Gitea users get different behaviour from every other host:

1. apps/web/src/lib/openPullRequestLink.ts (inline comment) — Gitea PR URLs are now readable for opening links, but apps/web/src/pullRequestReference.ts still rejects them for input, while the input placeholder promises "PR URL, checkout command, or #42".

2. apps/web/src/components/pullRequest/pullRequestDetail.logic.ts:855 — TOOL_NOISE replaces content-free host errors with an actionable hint for github|gitlab|bitbucket|azure devops, but the new provider's GiteaCliCommandError.detail is "Gitea CLI command failed." (apps/server/src/sourceControl/GiteaCli.ts:121), which no pattern matches. A failed Gitea action therefore surfaces the bare "Gitea CLI command failed." string where the other hosts surface the hint. Smallest fix is to include gitea in the alternation:

- /^(github|gitlab|bitbucket|azure devops)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,+ /^(github|gitlab|bitbucket|azure devops|gitea)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,

Minor, optional: the "Add project" command item's searchTerms (apps/web/src/components/CommandPalette.tsx:1547) lists github/gitlab/bitbucket/azure/devops but not gitea, so typing "gitea" no longer reaches the flow that now offers a Gitea source.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a large, cross-cutting Gitea integration with new authenticated repository, pull-request, checkout, and publishing workflows across production server and client paths. A remaining error-classification concern may cause missing pull requests to surface as generic command failures, so the runtime behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[MDragonryu]

Addressed the review findings in :\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout , and required a real NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[MDragonryu]

Addressed the review findings in commit 3e5118d:\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing tea executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout --force, and required a real tea login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Service definition, dependency acquisition (GiteaCli/GiteaSourceControlProvider both acquire their deps with yield* and expose make/layer), namespace imports, and the registry/layer wiring all look consistent with the sibling providers. Two error-modelling points below.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit 3f98c41:\n\n- createPullRequest no longer supplies a PR reference to HTTP error mapping, so a create-time 404 is a GiteaCliCommandError; existing get/checkout PR 404s remain not-found\n- listPullRequests now requests sort=recentupdate, keeping current-branch PR discovery within the bounded page window\n\nThe focused Linux devcontainer suite now passes 8 files and 164 tests.

[MDragonryu]

Follow-up Effect cleanup pushed in commit c0599af:\n\n- removed the redundant single-valued list decode operation field\n- removed the manufactured non-array JSON Error; decoder failures now carry the real schema failure while malformed JSON retains the real parse exception\n\nThe focused Linux devcontainer suite remains green: 8 files, 164 tests.

[macroscopeapp]

One finding: the new tea branch in classifyNonZeroExit changes backend error classification but has no focused test, and no tea rule produces not-found, so GiteaCli.checkoutPullRequest's not-found mapping is unreachable in production. Everything else in the new Gitea service modules follows the conventions (subpath namespace imports, inline Context.Service interface, make acquiring VcsProcess/GiteaCli from the environment, Schema.TaggedErrorClass errors with structural attributes and preserved cause, exported Schema.is predicate, layer at the bottom).

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

This changes backend failure classification (a tea exit mentioning "no available login" now surfaces as GiteaCliAuthenticationError rather than GiteaCliCommandError), but VcsProcess.test.ts has no case for it even though it already covers the analogous authentication and rate-limited phrases. Consider adding a focused case asserting failureKind: "authentication" for command: "tea" with that stderr, plus one asserting another command with the same phrase stays command-failed (the reason the rule is scoped to tea).

Related: no tea branch exists in the not-found block below, so classifyNonZeroExit never returns not-found for tea. GiteaCli.checkoutPullRequest's GiteaPullRequestNotFoundError.fromVcsError path is therefore only reachable in the unit test that hand-builds failureKind: "not-found"; a real tea pulls checkout 9999 failure maps to GiteaCliCommandError. Worth either adding the tea not-found phrases here or dropping the unreachable branch.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit d257b11:\n\n- full PR URL checkout now verifies the URL repository against the current Gitea repository before invoking tea, preserving same-repository and numeric checkout behavior\n- public github.com and bitbucket.org /pulls/ URLs are excluded from the generic Gitea reference parser while self-hosted lookalikes remain supported\n- added regression coverage for the repository guard and URL parsing\n\nVerification: 8 focused Linux devcontainer test files, 168 tests passed; targeted server/web TypeScript checks completed.

[macroscopeapp]

One new finding on the Gitea CLI error model, plus one earlier finding that is still open (see below). Everything else in the Gitea service/provider pair follows the conventions: namespaced effect/* imports, Context.Service with an inline interface, exported make/layer, dependencies acquired via yield* VcsProcess.VcsProcess / yield* GiteaCli.GiteaCli, structured Schema.TaggedErrorClass failures with real causes preserved and messages derived from stable attributes, and Schema.Union + Schema.is for the error predicate.

Still open from a previous run (not re-commented): apps/server/src/vcs/VcsProcess.ts changes non-zero-exit classification so a tea failure mentioning "no available login" is now categorized as authentication, and apps/server/src/vcs/VcsProcess.test.ts still has no case covering it (nor a case proving another command with the same phrase stays command-failed). Backend behavior changes should carry focused tests.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up test/convention fixes pushed in commit 556ce2d:\n\n- removed the redundant single-value Gitea pull-request decode operation field\n- added focused coverage for tea no-available-login authentication classification and the non-tea negative case\n\nVerification: 9 focused Linux devcontainer test files, 182 tests passed.

[macroscopeapp]

Reviewed the changed web UI surfaces for the Gitea provider addition (CommandPalette.tsx, GitActionsControl.tsx, SourceControlSettings.tsx, sourceControlPresentation.ts, pullRequestLinkContextMenu.ts, pullRequestDetail.logic.ts, openPullRequestLink.ts, pullRequestReference.ts). Provider enumerations, labels, icons and readiness maps are consistent, and the reference parser gap flagged on the earlier revision is now closed.

Two findings, one behavioral:

1. openPullRequestLink.ts now claims Gitea /pulls/{n} URLs, which makes those links open the in-app change-request surfaces even though this build registers no Gitea pull-request provider — the reader lands on the "Could not load pull requests" empty state instead of the host page they previously got in the browser.
2. GitActionsControl.tsx uses the literal "gitea" as the publish-dialog host, which is rendered as a hostname prefix when discovery reports no host.

^{Posted via Macroscope — UI Consistency}

[MDragonryu]

Final review cycle for 556ce2d is complete. Cursor Bugbot, Macroscope Correctness, Effect Service Conventions, and UI Consistency are green; the Approvability check completed neutral with correctness checked and eligibility unchecked. No new inline comments were posted on the current head. The worktree is clean and the PR is ready for human review.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16d32bc. Configure here.}

[macroscopeapp]

Two findings, both in the Source Control settings copy that this PR reworked to make room for Gitea's tea login add hint. The rest of the Gitea UI wiring (neutral GitPullRequestIcon for the unbranded provider, resolvePublishHost host fallback, /pulls/ link handling) looks consistent with the existing provider patterns.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

login add is a tea-only subcommand, but this helper renders the unauthenticated row for every provider, so GitHub now reads "Run gh login add", GitLab "Run glab login add" and Azure DevOps "Run az login add" — none of those commands exist (gh auth login, glab auth login, az login). The copy that was replaced was deliberately executable-agnostic.

Consider keeping the neutral phrasing here (or threading a per-provider auth command through the discovery spec) so only Gitea gets the tea login add wording:

Suggested change

	if(executable!==null){
	return`${label} is not authenticated on this server. Run \`${executable} login add\` on the server host to enable change request features.`;
	return`${label} is not authenticated on this server. Sign in or configure credentials using the \`${executable}\` tool on the server host to enable change request features.`;

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

We do not have a current support commitment for Gitea. This 39-file branch would add a source control CLI, discovery, repository operations, settings, contracts, icons, and a permanent compatibility obligation.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[MDragonryu]

Summary

• add Gitea discovery and authentication through tea
• implement repository, branch, pull-request, and provider operations
• wire Gitea through server, web, mobile, contracts, Git actions, and documentation
• add focused coverage for CLI parsing, provider behavior, registry discovery, and source-control contracts

Testing

• CI=true pnpm exec vp test run apps/server/src/sourceControl/GiteaCli.test.ts apps/server/src/sourceControl/GiteaSourceControlProvider.test.ts apps/server/src/sourceControl/giteaLogins.test.ts apps/server/src/sourceControl/SourceControlProviderRegistry.test.ts packages/shared/src/sourceControl.test.ts packages/contracts/src/sourceControl.test.ts
• 6 test files passed, 109 tests passed
• live validation completed against a fresh Gitea container with repository, commit/push, and three pull-request scenarios

Notes

Gitea support uses the authenticated tea CLI and preserves the existing provider architecture across server and clients.

---

Note

Medium Risk
Changes git stacked actions, PR creation/deduping, and remote provider resolution; behavior is heavily tested but errors could still mis-route remotes or mishandle tea HTTP responses.

Overview
Adds first-class Gitea support end-to-end so remotes no longer resolve to unknown and Commit, push & create PR works against Gitea hosts.

On the server, a new GiteaCli layer wraps the tea tool (API calls with HTTP status parsing because tea api exits 0 on errors, client-side PR list filtering/pagination, repo publish routing to user/repos vs orgs/.../repos). GiteaSourceControlProvider plugs into the existing registry with CLI discovery from tea logins list and host-based refinement of otherwise-unknown self-hosted remotes when tea is logged into that host.

Contracts, shared remote detection (gitea.com / *gitea* hosts), web and mobile add-project/publish/settings flows, and docs are extended for gitea. Publish UI uses discovery for hostname when there is no canonical host. In-app deep links still skip Gitea (parseChangeRequestUrl does not claim /pulls/{n}), while checkout/reference parsing accepts Gitea URLs and tea pulls checkout.

VcsProcess now treats tea’s “no available login” stderr as an authentication failure.

^{Reviewed by Cursor Bugbot for commit d1b9069. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Gitea source-control provider across backend, web, and mobile

• Implements GiteaCli wrapper around the tea CLI in GiteaCli.ts, covering PR list/get/create, repo creation, clone URLs, default branch, and checkout, with typed errors and HTTP status mapping.
• Adds GiteaSourceControlProvider in GiteaSourceControlProvider.ts implementing the provider contract, plus discovery and auth parsing based on tea logins list output.
• Wires Gitea into the server provider registry and WebSocket RPC layers in server.ts and ws.ts.
• Updates web, mobile, and shared packages: command palette, publish dialog, PR reference parsing, settings UI, icons, and provider detection.
• Risk: new 'gitea' literal added to SourceControlProviderKind schema in sourceControl.ts; out-of-tree contract consumers must regenerate schemas to decode the new kind.

^{Macroscope summarized d1b9069.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e4dce5a6-b2ec-4eb6-81ff-3ae86dc8f69e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Structure, namespace imports, Context.Service + inline interface, make/layer, and environment-based dependency acquisition all look right, and the test-only service-instance injection in GitManager.test.ts is a legitimate seam. Three findings on error modeling in apps/server/src/sourceControl/GiteaCli.ts.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI Consistency: 2 findings

Provider plumbing for the web client is otherwise complete and consistent (icon maps, labels, path hints, readiness, publish host, "Open on Gitea"). Two web surfaces that key off provider identity were not extended with the new kind, so Gitea users get different behaviour from every other host:

1. apps/web/src/lib/openPullRequestLink.ts (inline comment) — Gitea PR URLs are now readable for opening links, but apps/web/src/pullRequestReference.ts still rejects them for input, while the input placeholder promises "PR URL, checkout command, or #42".

2. apps/web/src/components/pullRequest/pullRequestDetail.logic.ts:855 — TOOL_NOISE replaces content-free host errors with an actionable hint for github|gitlab|bitbucket|azure devops, but the new provider's GiteaCliCommandError.detail is "Gitea CLI command failed." (apps/server/src/sourceControl/GiteaCli.ts:121), which no pattern matches. A failed Gitea action therefore surfaces the bare "Gitea CLI command failed." string where the other hosts surface the hint. Smallest fix is to include gitea in the alternation:

- /^(github|gitlab|bitbucket|azure devops)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,+ /^(github|gitlab|bitbucket|azure devops|gitea)?\s*(cli|api)?\s*(command\s*)?failed\.?$/iu,

Minor, optional: the "Add project" command item's searchTerms (apps/web/src/components/CommandPalette.tsx:1547) lists github/gitlab/bitbucket/azure/devops but not gitea, so typing "gitea" no longer reaches the flow that now offers a Gitea source.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a large, cross-cutting Gitea integration with new authenticated repository, pull-request, checkout, and publishing workflows across production server and client paths. A remaining error-classification concern may cause missing pull requests to surface as generic command failures, so the runtime behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[MDragonryu]

Addressed the review findings in :\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout , and required a real NAME:
tea - command line tool to interact with Gitea

USAGE:
tea [global options] [command [command options]]

VERSION:
Version: �[1m0.15.1�[0m golang: 1.26.5 go-sdk: v1.2.0

DESCRIPTION:
tea is a productivity helper for Gitea. It can be used to manage most entities on
one or multiple Gitea instances & provides local helpers like 'tea pr checkout'.

tea tries to make use of context provided by the repository in $PWD if available.
tea works best in a upstream/fork workflow, when the local main branch tracks the
upstream repo. tea assumes that local git state is published on the remote before
doing operations with tea. Configuration is persisted in $XDG_CONFIG_HOME/tea.

COMMANDS:
help, h Shows a list of commands or help for one command

ENTITIES:
issues, issue, i List, create and update issues
pulls, pull, pr Manage and checkout pull requests
labels, label Manage issue labels
milestones, milestone, ms List and create milestones
releases, release, r Manage releases
times, time, t Operate on tracked times of a repository's issues & pulls
organizations, organization, org List, create, delete organizations
repos, repo Manage repositories
branches, branch, b Consult branches
actions, action Manage repository actions
wiki Manage repository wiki pages
webhooks, webhook, hooks, hook Manage webhooks
comments, comment, c Manage comments on issues and pull requests

HELPERS:
open, o Open something of the repository in web browser
notifications, notification, n Show notifications
clone, C Clone a repository locally
api Make an authenticated API request

MISCELLANEOUS:
whoami Show current logged in user
admin, a Operations requiring admin access on the Gitea instance

SETUP:
logins, login Log in to a Gitea server
logout Log out from a Gitea server
ssh-keys, ssh-key Manage SSH public keys

GLOBAL OPTIONS:
--debug, --vvv Enable debug mode
--help, -h show help
--version, -v print the version login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[MDragonryu]

Addressed the review findings in commit 3e5118d:\n\n- tightened Gitea execution error structure and HTTP status handling\n- classified only missing tea executables as unavailable\n- handled malformed PR URLs and preserved raw pagination counts\n- matched fork source owners, honored checkout --force, and required a real tea login user\n- added Gitea pull-request URL/CLI reference recognition and UI noise/search coverage\n- preserved public GitHub/Bitbucket URL behavior while allowing self-hosted lookalike hosts to fall through to Gitea parsing\n\nVerification in the Linux devcontainer: 8 focused test files, 161 tests passed; server and web TypeScript checks completed with only existing repository suggestions.

[macroscopeapp]

Reviewed the new Gitea service modules against the Effect service conventions. Service definition, dependency acquisition (GiteaCli/GiteaSourceControlProvider both acquire their deps with yield* and expose make/layer), namespace imports, and the registry/layer wiring all look consistent with the sibling providers. Two error-modelling points below.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit 3f98c41:\n\n- createPullRequest no longer supplies a PR reference to HTTP error mapping, so a create-time 404 is a GiteaCliCommandError; existing get/checkout PR 404s remain not-found\n- listPullRequests now requests sort=recentupdate, keeping current-branch PR discovery within the bounded page window\n\nThe focused Linux devcontainer suite now passes 8 files and 164 tests.

[MDragonryu]

Follow-up Effect cleanup pushed in commit c0599af:\n\n- removed the redundant single-valued list decode operation field\n- removed the manufactured non-array JSON Error; decoder failures now carry the real schema failure while malformed JSON retains the real parse exception\n\nThe focused Linux devcontainer suite remains green: 8 files, 164 tests.

[macroscopeapp]

One finding: the new tea branch in classifyNonZeroExit changes backend error classification but has no focused test, and no tea rule produces not-found, so GiteaCli.checkoutPullRequest's not-found mapping is unreachable in production. Everything else in the new Gitea service modules follows the conventions (subpath namespace imports, inline Context.Service interface, make acquiring VcsProcess/GiteaCli from the environment, Schema.TaggedErrorClass errors with structural attributes and preserved cause, exported Schema.is predicate, layer at the bottom).

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

This changes backend failure classification (a tea exit mentioning "no available login" now surfaces as GiteaCliAuthenticationError rather than GiteaCliCommandError), but VcsProcess.test.ts has no case for it even though it already covers the analogous authentication and rate-limited phrases. Consider adding a focused case asserting failureKind: "authentication" for command: "tea" with that stderr, plus one asserting another command with the same phrase stays command-failed (the reason the rule is scoped to tea).

Related: no tea branch exists in the not-found block below, so classifyNonZeroExit never returns not-found for tea. GiteaCli.checkoutPullRequest's GiteaPullRequestNotFoundError.fromVcsError path is therefore only reachable in the unit test that hand-builds failureKind: "not-found"; a real tea pulls checkout 9999 failure maps to GiteaCliCommandError. Worth either adding the tea not-found phrases here or dropping the unreachable branch.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up fixes pushed in commit d257b11:\n\n- full PR URL checkout now verifies the URL repository against the current Gitea repository before invoking tea, preserving same-repository and numeric checkout behavior\n- public github.com and bitbucket.org /pulls/ URLs are excluded from the generic Gitea reference parser while self-hosted lookalikes remain supported\n- added regression coverage for the repository guard and URL parsing\n\nVerification: 8 focused Linux devcontainer test files, 168 tests passed; targeted server/web TypeScript checks completed.

[macroscopeapp]

One new finding on the Gitea CLI error model, plus one earlier finding that is still open (see below). Everything else in the Gitea service/provider pair follows the conventions: namespaced effect/* imports, Context.Service with an inline interface, exported make/layer, dependencies acquired via yield* VcsProcess.VcsProcess / yield* GiteaCli.GiteaCli, structured Schema.TaggedErrorClass failures with real causes preserved and messages derived from stable attributes, and Schema.Union + Schema.is for the error predicate.

Still open from a previous run (not re-commented): apps/server/src/vcs/VcsProcess.ts changes non-zero-exit classification so a tea failure mentioning "no available login" is now categorized as authentication, and apps/server/src/vcs/VcsProcess.test.ts still has no case covering it (nor a case proving another command with the same phrase stays command-failed). Backend behavior changes should carry focused tests.

^{Posted via Macroscope — Effect Service Conventions}

[MDragonryu]

Follow-up test/convention fixes pushed in commit 556ce2d:\n\n- removed the redundant single-value Gitea pull-request decode operation field\n- added focused coverage for tea no-available-login authentication classification and the non-tea negative case\n\nVerification: 9 focused Linux devcontainer test files, 182 tests passed.

[macroscopeapp]

Reviewed the changed web UI surfaces for the Gitea provider addition (CommandPalette.tsx, GitActionsControl.tsx, SourceControlSettings.tsx, sourceControlPresentation.ts, pullRequestLinkContextMenu.ts, pullRequestDetail.logic.ts, openPullRequestLink.ts, pullRequestReference.ts). Provider enumerations, labels, icons and readiness maps are consistent, and the reference parser gap flagged on the earlier revision is now closed.

Two findings, one behavioral:

1. openPullRequestLink.ts now claims Gitea /pulls/{n} URLs, which makes those links open the in-app change-request surfaces even though this build registers no Gitea pull-request provider — the reader lands on the "Could not load pull requests" empty state instead of the host page they previously got in the browser.
2. GitActionsControl.tsx uses the literal "gitea" as the publish-dialog host, which is rendered as a hostname prefix when discovery reports no host.

^{Posted via Macroscope — UI Consistency}

[MDragonryu]

Final review cycle for 556ce2d is complete. Cursor Bugbot, Macroscope Correctness, Effect Service Conventions, and UI Consistency are green; the Approvability check completed neutral with correctness checked and eligibility unchecked. No new inline comments were posted on the current head. The worktree is clean and the PR is ready for human review.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 16d32bc. Configure here.}

[macroscopeapp]

Two findings, both in the Source Control settings copy that this PR reworked to make room for Gitea's tea login add hint. The rest of the Gitea UI wiring (neutral GitPullRequestIcon for the unbranded provider, resolvePublishHost host fallback, /pulls/ link handling) looks consistent with the existing provider patterns.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

login add is a tea-only subcommand, but this helper renders the unauthenticated row for every provider, so GitHub now reads "Run gh login add", GitLab "Run glab login add" and Azure DevOps "Run az login add" — none of those commands exist (gh auth login, glab auth login, az login). The copy that was replaced was deliberately executable-agnostic.

Consider keeping the neutral phrasing here (or threading a per-provider auth command through the discovery spec) so only Gitea gets the tea login add wording:

Suggested change

	if(executable!==null){
	return`${label} is not authenticated on this server. Run \`${executable} login add\` on the server host to enable change request features.`;
	return`${label} is not authenticated on this server. Sign in or configure credentials using the \`${executable}\` tool on the server host to enable change request features.`;

^{Posted via Macroscope — UI Consistency}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

We do not have a current support commitment for Gitea. This 39-file branch would add a source control CLI, discovery, repository operations, settings, contracts, icons, and a permanent compatibility obligation.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.