See your PR through
A PR you open is yours until it's merged or closed. Nothing GitHub does on it reaches you: you only wake when a board message arrives. So you check on it yourself, with messages you schedule in the thread you built it for. Each one wakes you when it's posted.
Right after gh pr create
Schedule its check-ins, each with --no-sync so they stay out of Slack. Every one is a whole
turn of yours, and most find nothing, so they thin out as the PR ages:
- While its checks run:
vb schedule <id> "Check on <owner/repo>#<N>" --every 10m --times 6 --no-sync - Its first day:
vb schedule <id> "Check on <owner/repo>#<N>" --in 2h --every 4h --times 6 --no-sync - The week after:
vb schedule <id> "Check on <owner/repo>#<N>" --in 2d --every 1d --times 6 --no-sync
A reply in the thread still reaches you at once, so nobody waits on a check-in to get your attention. The check-ins skill has the rest: one set per open thing, and what to do when one wakes you.
On each check-in
Start on GitHub, not the board: the board doesn't show what changed on the PR.
gh pr view <N> --repo <owner/repo> --json state,reviewDecision,reviews,comments,statusCheckRollup
gh api repos/<owner/repo>/pulls/<N>/comments # inline review commentsThen move it forward:
- Its checks have finished: cancel what's left of the first set.
- A failing check: read why. If your change broke it, fix it and push. If it's flaky or unrelated, re-run it once; if it fails the same way again, say which check and why in the thread instead of re-running it.
- Review comments: address each one, with a fix pushed or a reply on GitHub where you disagree.
- Waiting on a review for more than a day: ask once in the thread, mentioning whoever should review it. Don't ask again.
- Approved, green, and nothing left open: merge it if the repo's rules let you and the person who asked wants it merged. Otherwise say it's ready, and who can merge it.
- No longer wanted, replaced by another PR, or stuck on a decision nobody's making: say so, and close it once someone agrees.
- Merged or closed: say so in one line, and cancel its check-ins:
vb schedules <id>, thenvb schedule cancel <schedule>for each. When that settles what the thread asked for, mark the thread resolved: ✅ on its root. - The last check-in, and it's still open: say once where it stands and who it's waiting on,
and ask whether to keep it. Schedule more only if someone wants it kept. It's the last when
vb schedules <id>shows none pending for the PR: the first two sets end long before.
A check-in that finds nothing new posts nothing.