Repository navigation
playbooks: pass the resolved owner/repo on every gh call (fork-safe) #169
Description
In a fork with an upstream remote, gh can resolve its default repo to the parent. Here it listed issues from the read-only upstream. Sessions then carried a hand-written standing rule to pass -R owner/repo on every call.
Proposal: wherever a pstack playbook (babysit, opening-a-pr, merge-gate, the watcher) resolves the forge and repo, pass that resolved owner/repo explicitly on every gh call, instead of relying on gh's default-repo inference. This is fork-safe in any consumer repo.
Source: /reflect over 2026-09-30..10-07.
Activity
fix(poteto-mode): count FAIL rounds in merge-gate and pass the resolv…
fix(poteto-mode): count FAIL rounds in merge-gate and pass the resolv…
fix(poteto-mode): count FAIL rounds in merge-gate and pass the resolv…
fix(poteto-mode): count FAIL rounds in merge-gate and pass the resolv…
fix(poteto-mode): count FAIL rounds in merge-gate and pass the resolv…
fix(poteto-mode): correct failure-round tracking and PR repository se…
mdsmithaustin commentedon Oct 15, 2026
The remaining accepted repository-binding corrections merged in #243. Together with #205, this resolves the audited caller set by using the resolved origin repository and host explicitly. Automatic fork-to-upstream target selection remains a separate proposal in #210.