Track GitHub PRs and issues for repos not on disk #77
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#77
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:43Z - https://github.com/coilysiren/repo-recall/issues/11
Gap
Today
repo-recallonly knows about repos with a local clone underREPO_RECALL_CWD. PRs and issues in repos Kai contributes to but hasn't cloned (e.g.urfave/cli,backstage/backstage,dagger/dagger) are invisible.gh dashcovers this case via arbitrary GitHub search queries.Proposal
Add a "GitHub state I care about, regardless of disk" view backed by a small, configurable set of
gh searchqueries. Strawman:Each becomes a tab/section. Repos not on disk would still link out to
github.comrather than to a local repo card.Caveats
gh run list. Worth a separateghrate-limit budget.ghis unauthenticated or rate-limited (existing pattern).Relationship to #10
The cross-repo review queue issue is local-clone-scoped. This one is the broader follow-on: "show me GitHub state I care about even when I don't have the repo on disk." Land the simpler one first, this one second.
Iceboxed in the 2026-05-29 backlog burn-down: Track repos not on disk; speculative scope expansion. Reopen anytime if it becomes real.