3 Commits

Include renames

Author	SHA1	Message	Date
Omar Sobh	637e1bdd69	repos: sidebar actions (sync/edit/remove) + edit modal ... Sidebar: - Each connection header now has three inline icon buttons: Sync now (spins while in flight), Edit (opens the modal), Remove (opens an inline confirm strip). Removes cascade repos via ON DELETE CASCADE. - The connection's last_sync_error surfaces as a red inline banner under the header — no more 'error status with nowhere to see why'. - Sync is POST /api/repos/connections/:id/sync (already existed); after either sync or delete the sidebar re-fetches so state stays consistent. Edit modal (RepoConnectionEditModal): - Loads GET /api/repos/connections/:id, pre-fills owner/base_url/label - PATCHes only the fields that actually changed; empty string on a Some(&str) field sends explicit null so the backend clears it - Sync-now + Remove reachable from inside the modal too - Rotating the token is out of scope: the modal says as much and points the user at delete + re-create through the wizard (the broker doesn't expose an update path, and rotating in place would require duplicating the whole broker->store_secret flow here) Backend: - GET /api/repos/connections/:id — same ConnectionSummary shape - PATCH /api/repos/connections/:id — owner/base_url use Option<Option<T>> double-nesting so 'omit = leave alone' and 'null = clear' round-trip distinctly through serde - repo_connections::update with COALESCE-per-field so the SQL matches the double-Option semantics without an OR-chain per field	2026-07-07 17:55:20 -07:00
Omar Sobh	e858a7f92f	repos: Gitea provider (first-class) — sync + wizard default ... Fleet's Gitea (git.redclaw.dev) hosts most of this workspace's repos, so Gitea gets the same inline sync treatment GitHub already had. Backend sync_gitea: - base_url is required — Gitea has no shared 'gitea.com'; we accept either the instance root (auto-appends /api/v1) or the fully-formed API base if the user already included the suffix - /orgs/{owner}/repos when owner set, /repos/search when not (with the {data: [...], ok: bool} envelope Gitea wraps that endpoint in) - 404 with an owner surfaces as 'org not found or PAT lacks access', same UX as GitHub - 50/page, capped at 20 pages (~1000 repos); short page terminates - upsert_gitea_repo tolerates the small field-name differences (stars_count vs stargazers_count, owner.login vs owner.username on older versions) Frontend wizard: - Gitea listed first — matches the workspace's actual usage - Default provider selection is now gitea - Token-input placeholder tailored per provider (Gitea's is 'Settings → Applications → Generate New Token (repo)') GitLab still returns 'not yet supported' — that's the next follow-up.	2026-07-07 15:11:30 -07:00
Omar Sobh	6d087bf537	repos: backend — schema, /api/repos routes + GitHub sync provider ... Migration 0034: two tables. repo_connections carries the workspace's per-provider config (owner, base_url, label, last_synced_at, last_sync_error) and points at an app_connections row for the PAT. repos is the per-connection cache with (connection_id, external_id) unique so upsert is idempotent across re-syncs. Cascading deletes clean up cleanly on connection removal. cm-secrets grows a FetchAuthorized op — GET with the stored PAT injected as bearer, returns status + JSON body without ever exposing the credential to cm-api. This is the least-privilege door for read-only provider APIs (list repos), distinct from the InvokeHttp path that still requires a single-use approval grant for outbound writes. cm-api::routes::repos wires: - POST /api/repos/connections (broker store_secret + insert both rows + initial sync + mark_synced) - GET /api/repos/connections - DELETE /api/repos/connections/:id - POST /api/repos/connections/:id/sync - GET /api/repos (500 cap, newest provider_updated first) - GET /api/repos/:id (full detail incl. clone_url + html_url) GitHub provider inline for v1 — paginated pull of /orgs/:owner/repos (when owner set) or /user/repos (when absent), 100/page, capped at 20 pages (~2k repos) to keep first-sync latency bounded. Non-2xx surface back to the caller as sync_error; parse failures are best-effort per repo (skipped, logged, don't abort the batch). Gitea + GitLab providers land in a follow-up — mostly URL swap + response-shape adapter.	2026-07-07 14:52:47 -07:00