watchpr: add --max-wait with distinct timeout exit code #25
Reference in New Issue
Block a user
Delete Branch "benvin/watchpr-max-wait"
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?
watchpr runs as a background command that the harness kills at a 2h cap; a killed watcher looks like a crash and is not restarted, so PR watching silently stops.
--max-wait <duration>(same forms as--interval, 0 = unlimited)timeout: no change within <d>plus current PR states ({"timeout":true,...}under--json) and exit 3--max-wait 110mrestart-on-3 orchestrator pattern--once --max-wait Xis accepted and silently ignored → reject it (--max-wait is incompatible with --once) or state in the flag help that --once ignores it.errTimedOut-> 3, parse/poll errors -> 1; only the parse-error side is covered) → test that runWatch returns errTimedOut on a closed tick channel, or factor the exit-code mapping out of main() and test it.No findings.