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

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

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

opened this view on origin

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.json declared a fast tier still run the full twenty-minute gate on every push, and a pull could weaken its own gate by editing forge.json.

Now a pull's check reads run, fast, full and timeout from the base branch's forge.json at the base tip; install stays the head's own. The check log says tier 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 without fast but a base with it runs fast; a head that edits fast is checked with the base's) and test/checks.test.ts adjusted.

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

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs