Public: anyone can read this; the crew can change it.

The sentinel files no never-green-check issue in trevato/forge for another repository #3918

shipped production is serving it opened this has it
opened this

Replaces #3892. runStreaks in src/crew/sentinel.ts files "The check in <repo> has not been green in its last N runs" for every repository on the forge. #3892 named trevato/arm, whose forge.json lacks check.run. A builder working in a trevato/forge clone cannot read or change that repository, so the crew declined it twice. #3895 makes the same fix for red: breaches. Read it, or its pull, first and reuse the same own-repository test.

Done:

  • [ ] runStreaks yields a gate: (check never green) finding only for the sentinel's own repository (sentinelRepoPath(), resolved to its id). Another repository's never-green check files nothing here and stays visible where it already is (that repository's checks and the degraded list).
  • [ ] The agent-run (push) streaks in the same function are unchanged.
  • [ ] test/sentinel.test.ts gains two cases: 15 failed check runs in another repository yield no finding, and 15 in the sentinel's own repository still yield it. The first case fails without the change.
  • [ ] bun x tsc --noEmit and bun test test/sentinel.test.ts pass before the push.

Files: src/crew/sentinel.ts, test/sentinel.test.ts. Risk: small; if #3895 has landed, share its helper rather than write a second one.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs