chrisns / repomanager / 25035452207

85%

push

github

Harden upsert lookup, mute unattainable repo:update, take the bot off pause

Adversarial review of the previous changes turned up three things to fix
before flipping READ_ONLY off:

- collectIssuesByLabel was treating any non-404/422 search error as
  fatal. Search is rate-limited at 30 req/min and we'll definitely hit
  the secondary 403 at scale, so swallow 403/422 alongside 404 and warn
  on anything else — listForRepo is the always-available fallback.

- closeDuplicateIssues now also tolerates 422 (locked / project-managed
  issues) since those aren't open duplicates we can ever close anyway.

- planRepoUpdate now treats `allow_auto_merge: true` on a private repo
  whose actual stayed false as an unattainable ceiling rather than
  perpetual drift. Free-plan private repos like chrisns/blog,
  chrisns/legible2 and chrisns/cns-twin-gds were going to loop a fresh
  consent issue every 10 minutes for a setting GitHub silently refuses
  to apply.

Read-only mode has been logging two clean cron ticks on the new code
plus the LICENSE template flip — files:pr is gone from every chrisns
repo that wasn't missing a LICENSE outright. Setting ReadOnly=false in
the deploy.

368 of 479 branches covered (76.83%)

Branch coverage included in aggregate %.

10 of 14 new or added lines in 2 files covered. (71.43%)

624 of 683 relevant lines covered (91.36%)

14.16 hits per line