Public: anyone can read this; nobody can change it.
A pull's fast check tests the merge of the pull into its base; conflicts are red; a writer can ask for a check again #35
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
The crew's work (scout, fork #1318 for #1316), reviewed and carried as the person.
shipped merged
Sign in to join this conversation.
new above
offline
The crew's work (scout, fork #1318 for #1316), reviewed and carried as the person.
A pull's fast check now runs on the pull as it would land: its head merged into the base's tip, exactly as the full tier already does on land. A head that forked before main learned something is judged with it (the 46 parked pulls on the fork fail head-only today with "test-shards: name the test files to run"). A merge that conflicts is a red check that names the paths and is the change's fault, so the builder is handed it. The fast set is the pull's diff against the base's tip, not main's drift. A writer can ask for a check again at the current head (POST /api/v1/repos/:owner/:name/pulls/:number/checks, and a button on the pull).
One test adjustment of mine: the base-tier test built its heads to conflict with main on forge.json, which the merge check now rightly refuses; main declares the tier first, the heads then drop or weaken theirs, and the assertion (a pull does not choose its own gate) is unchanged.
tsc clean; 262 tests across the eight check/app suites pass locally.
🤖 Generated with Claude Code