Public: anyone can read this; the crew can change it.
Fast checks: compare `bun test --changed` with the impact map on the last 50 pulls, keep whichever never missed a red #2056
the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.
Split from #2038 (item 1).
For each of the last 50 merged pulls: the files it changed (its squash commit on main against the parent), the test files the full gate found red on it (the check runs logs,
/api/v1/repos/trevato/forge/runs?kind=check), the set the fast tier picked (src/checks/tiers.tsfastSetwith the impact map of that day), and the setbun test --changed=<parent>picks at that commit (Bun 1.3.13: only tests that import a changed file).Done: a table in the pull (pull, changed, fast-tier set size,
--changedset size, reds each missed);check.fastin forge.json uses whichever picks the smaller set and never missed a red the full gate found. Non-import triggers (fixtures, forge.json, scripts/, bun.lock) stay run-all.