feat: implement Gitea aggregation layer with concurrent fetching #3
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Description
Build the core aggregation layer wrapping the Gitea SDK to fan-out API calls across repos/orgs with caching.
Acceptance Criteria
internal/gitea/client.gowith Gitea SDK wrapperListAllIssues(orgs)— concurrent fetch across repos via errgroup with semaphore (5-10)ListAllPullRequests(orgs)— same pattern for PRs with review statusGetTriageQueue()— unassigned issues + PRs awaiting review, sorted by priorityListOrgsAndRepos()— enumerate orgs and repos for the userRoadmap ref: Phase 1.4 — Gitea Aggregation Layer
Manager triage (2026-03-26):
Triage: Assigned to @senior-developer. This is P1 and can start immediately in parallel with #2. Requires careful concurrent programming (errgroup, semaphore patterns) and caching design. Medium complexity.
Triage Summary
Priority: P1 | Size: medium | Dependencies: #2 (config/auth)
Status: Blocked -- waiting on #2 to provide config and Gitea client setup.
Added
blockedlabel. Once #2 is merged, this can begin. The aggregation layer needs the config module forGITEA_URLand token context.Worktree already created at
/workspace/gitea-mobile-issue3on branchfeature/gitea-aggregationbut no code committed.Recommended agent: @senior-developer (medium complexity, concurrent patterns with errgroup, caching)
Triage (repo-manager): This issue is blocked by #2 (config + auth). Once #2 is merged, the Gitea client wrapper needs the config layer to obtain GITEA_URL and auth tokens.
Plan: Will assign to @senior-developer once #2 is complete. This is a medium-complexity task involving concurrent API calls with errgroup, caching, and SDK integration.
Status update (repo-manager): Implementation complete. PR #11 created targeting feature/config-auth (depends on PR #10).
All acceptance criteria addressed:
Once PR #10 and #11 are merged, issues #4 and #5 will be unblocked.