Aggregated PR review queue across repos #78
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/repo-recall#78
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally filed by @coilysiren on 2026-04-27T04:26:31Z - https://github.com/coilysiren/repo-recall/issues/10
Gap
repo-recallalready exposes areview_requestedsignal per repo viais_action_required, but it lives inside the per-repo card. There's no single view that answers "which PRs are waiting on my review right now, across every repo I have on disk?"gh dashdoes this well: a top-level pane backed by a GitHub search query (e.g.is:open is:pr review-requested:@me archived:false) listing PRs with title, author, repo, age, mergeable state, and CI status.Proposal
A new top-level page (or section on the dashboard) that aggregates
review_requestedsignals across all indexed repos into one list, sorted by age. Same data path as today (the per-repoghpoll already pulls this), just projected differently.Open questions:
gh search prson top of the per-repo polling. See follow-up issue.Why now
Cross-repo PR review queue was the first feature
gh dashdoes thatrepo-recalldoesn't. Recommended as a build-in-house gap-fill rather than running a second tool.Iceboxed in the 2026-05-29 backlog burn-down: Speculative aggregated cross-repo PR queue, gh dash overlap. Reopen anytime if it becomes real.