Public: anyone can read this; nobody can change it.
A pull's check tier and timeout come from the base branch's forge.json #34
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
Scout's fix for the fork's #1275, carried upstream as written (fork pull #1276, commit 565306f2), reviewed by the owner's steward.
shipped merged
Sign in to join this conversation.
new above
offline
Scout's fix for the fork's #1275, carried upstream as written (fork pull #1276, commit 565306f2), reviewed by the owner's steward.
After 0.7.67 the forge reads a pull's check tier from the commit it checks, so the forty-odd pulls branched before
forge.jsondeclared a fast tier still run the full twenty-minute gate on every push, and a pull could weaken its own gate by editingforge.json.Now a pull's check reads
run,fast,fullandtimeoutfrom the base branch'sforge.jsonat the base tip;installstays the head's own. The check log saystier fast from main@<sha>. The fork point for the fast diff comes from the same base tip.Tests:
test/check-tiers.test.ts(a head withoutfastbut a base with it runs fast; a head that editsfastis checked with the base's) andtest/checks.test.tsadjusted.Why it matters now: 43 checks are queued on the fork at a median of 20 minutes each; with this live they run in minutes.
🤖 Generated with Claude Code