Submatter/plans/Plan-automation-foundation/Epic-connected-repos/Epic-connected-repos.md
Randall Stillwell 35def387ae docs(plans): add Autensa benchmark tasks to automation foundation roadmap
Map reliability, operator UX, and spend-control follow-ons onto epics 1–9
so worker, webhooks, and fleet work have bead-scale task briefs.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-03 10:48:36 -05:00

1.7 KiB

kind slug title plan_slug status priority tenant_id cursor_epic_id updated_at
epic connected-repos Connected repos — paste remote URL, forge adapters automation-foundation done P1 global null 2026-08-03

Epic objective

Workspace admins connect git remotes (Forgejo, GitHub, GitLab, Bitbucket, future Origin) via paste URL UX. Store repo_links with forge_type, API base, and credentials reference. Provide a ForgeAdapter interface for clone metadata, open PR, and (later) webhooks.

See automation foundation discussion: Vercel/Coolify-style “show me your repo.”

In scope / out of scope

In scope

  • connected_repos (or repo_links) Drizzle table, workspace-scoped.
  • tRPC CRUD + “test clone” (shallow fetch).
  • Settings UI: connect / disconnect / list.
  • Forge adapter trait + implementations: forgejo, github (minimum two).

Out of scope

  • Webhook receivers (Epic 8).
  • Orchestrator clone logic (Epic 6 consumes this table).

Dependencies

  • Workspace admin auth patterns (existing).

Blocks

  • Epic 6 (orchestrator), Epic 7 (worker).

Acceptance criteria

  • Admin pastes Forgejo URL; Echodo stores link and detects forge_type.
  • Worker/orchestrator can read git_remote_url + default branch from API.

Tasks

Follow-on tasks (Autensa benchmark)

Task Link
Repo setup preflight tab Task-repo-setup-preflight