P1: read the real gitea backlog into the app #36
Reference in New Issue
Block a user
No description provided.
Delete Branch "p1/backlog-read"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
CommiTea now shows its own real backlog. This is the first end of the sync loop — the app reads live gitea data instead of demo fixtures, so the dogfood is real: The pot renders CommiTea's actual issues.
What's here
@commitea/core— the client (#1) gainslistIssues(paginated, PRs excluded) andlistMilestones; a purelifecycle-v0mapper places issues into columns from a single list read (closed→done, labelled/milestoned→triage, bare→diagnosis).steeping/reviewneed the issue timeline (P1-5) and stay empty rather than guess. +10 unit tests (30 total in core).'self'anyway). Config resolves from env /.env.local; gated off underCOMMITEA_E2Eso the committed e2e suite stays deterministic on fixtures.useBacklog()reconciles once on mount through the bridge;issuesToBoardColumnsshapes real issues into The pot. Board takes optional real columns + a loading state and falls back to demo fixtures when no token is configured.Verification
yarn typecheckclean (core + desktop)GITEA_LIVE=1) launches against the real repo — the board renders the actual 25 open + 9 closed issues. Screenshot confirmed.Next slices (P1)
ChangeSourcepoll/reconcile-on-a-timerConfig is dev-only for now (env /
.env.local); wiring Settings/Onboarding to store it is a follow-up.🤖 Generated with Claude Code