Lanes
gstack lanes no longer report done while remote tests wait
Test tier still waiting on a remote runlane reported done
Now, naming the
--remote command that clears itunfinishedIn the contract every lane inherits: autoplan reviewer prompts,
gstack-autoplan contract and /spec.LanesGate waitReuseYour setup
garrytan/gstack · CHANGELOG.md 1.91.133.0
gstack lanes from autoplan and spec no longer report done while their test tier still waits on a remote run. That wait now counts as unfinished, and the lane names the command that clears it.
Gate wait
gstack's paid PR gate now waits for free tests and 10 quiet minutes
Quiet since the last push10 min
Free Tests on the same headmust pass
$1,380
a week saved by the wait alone
0
paid slices when Free Tests are red
LanesGate waitReuseYour setup
garrytan/gstack · CHANGELOG.md 1.91.134.0
On a gstack pull request, the paid eval gate now waits for free tests to pass and ten quiet minutes. Failing free tests stop it before any paid work, saving about fourteen hundred dollars a week.
Reuse
A restamp or a main merge reuses the gate's green verdict
Only VERSION, package.json or CHANGELOG.md changedPASS (reused: restamp-only)
Main moved, your own diff byte-identicalPASS (reused: main moved)
If main changed a file your PR also changes, the full gate runs. Free Tests still run on every new head.
LanesGate waitReuseYour setup
garrytan/gstack · CHANGELOG.md 1.91.134.0
A pull request that only restamps, or takes a main merge that leaves its own diff unchanged, now reuses its last green gate. Touch a file main also changed, and the full gate runs.
Your setup
How many cores does the machine running your gstack lanes have?
CHANGELOG.md"If you…" notes for 1.91.134.0docs/pregate.mdthe remote test tierLanesGate waitReuseYour setup
garrytan/gstack · CHANGELOG.md 1.91.134.0 · 1.91.133.0
The upgrade notes say how to keep a reused gate when you restamp or merge main. So, how many cores does the machine running your gstack lanes have?
