gstack merge trains now land pull requests in any repo

gstack merge trains used to need gstack's own eval workflow. Now any repository can run one, gated by its own CI or a test on a Ubicloud machine, so a team stops merging one pull request at a time.

Slide text

gstack merge trains now land pull requests in any repo

workflows your own CI runs on every prefix of the train

command or a test command on a Ubicloud VM, under one spend cap

lands each green slot merges in order

Trains Culprit Review Rollback Worktree Budget Receipts Red main Skills Security Fixes

garrytan/gstack · CHANGELOG.md · 1.92.0.0

Before, a train only tested its tip, and finding the pull request that broke it took a bisect. Now every prefix is tested. The first red one names the culprit, and the pull requests ahead of it still land.

/ship review now runs one batched specialist that reads every checklist your diff calls for, sized to what the diff can break. It caught thirty-three of forty-one known blockers, where the old review caught twenty-seven.

For a few releases, /ship gave each reviewer a prepared packet instead of the code. Those reviewers caught about half the blockers, so they're gone. A pull request reviewed on those versions may still hide one.

Run /ship from a git worktree on a shared machine, and its reviewers used to review whatever branch the main checkout held. Now each reviewer names the tree it read, and a reply from the wrong tree is refused.

Give /ship a token cap and it now checks the cap before every step, where one run used to spend twice its cap. Each step is priced from this run's real spending, so a tight cap still lets cheap work through.

After you merge main into a reviewed branch, /ship checks whether your own code changed. If it didn't, it skips the review. A stacked pull request now keeps its review too, once its parent lands.

When main breaks for a reason outside your pull request, /ship now pauses until main is green, then you resume it. Your repo turns this on in its ship policy. On a merge train, the fix for main rides first.

/verify runs your checks and the tests /ship would pick, and fixes what breaks until they pass. /modernize recommends whether to rebase, rework, or close an aging pull request. /write-skill writes and slims your own skills.

A sealed-guard waiver used to match any commit that shared its first seven characters, and a matching commit takes minutes to generate. Waivers now need the full commit hash, so an old short one stops waiving.

A test that fails once and passes on a rerun now keeps your CI green. A reviewer that never saw your diff no longer counts as clean. And an unattended /ship asks before it bumps the version. I'd upgrade today, for reviews that catch more and merge trains in your own repo.