- All playbooks
- Restore a historical test set in one operation
Restore a historical test set in one operation
Restore a whole set of files with one Git command.
Company examples
How OpenAI used this technique
Read what OpenAI changed and follow the original sources.
Restore a historical test set in one operation
The Go SDK's compatibility script replaced 82 individual checkouts with one NUL-delimited tree listing and one literal-pathspec checkout. Tests absent from the baseline remain untouched.
82 checkouts became one; local run 198.66s to 88.63s together with the compile-only change below Source
- Use it when
- A script restores files with a separate Git invocation for each one.
- Before applying it
- Batching must keep literal paths and the handling of files that are absent from the baseline.
Company Playbooks
- Read Anthropic’s playbookRun only affected tests
- Read DoorDash’s playbookRun build and test in parallel, sharded across CI agents
- Read Linear’s playbookBenchmark the same job on faster hardware
- Read Mastra’s playbookStarSling runners for the slowest test workflow
- Read OpenAI’s playbookRank CI fixes by the minutes they save
- Read Ramp’s playbookMove a CPU-bound test suite to a faster CPU
- Read Shopify’s playbookLet an agent iterate against one CI metric
- Read Spotify’s playbookBuild arm64 on native arm64 runners
- Read Stripe’s playbookRun only the tests a change can reach
- Read Uber’s playbookBuild the merge-queue speculations most likely to be needed