chrisns / repomanager / 25019849355

85%

push

github

Add READ_ONLY kill switch and turn it on while we debug the planner

The cron has been creating a fresh consent issue per repo per tick because
the planner unconditionally proposes `bp:main`, `repo:update` and
`files:pr` without ever reading current repo state — only `planRulesets`
diffs against actual. Each apply succeeds, the next cron sees the same
"drift", and we re-issue the same consent.

Wire a READ_ONLY env var through to handler.js and gate every write path
(cron processRepo, webhook applyConsentedChanges). When set, we still
plan and log, but skip applyChanges, upsertConsentIssue and
markItemsApplied. Default the deploy to ReadOnly=true so the live bot
stays paused until we've actually fixed the planner drift checks.

283 of 377 branches covered (75.07%)

Branch coverage included in aggregate %.

6 of 21 new or added lines in 1 file covered. (28.57%)

541 of 589 relevant lines covered (91.85%)

14.6 hits per line