Bound stalled transfers and retry them
Linear replaced its checkout step with a composite action that retries with backoff and aborts a stalled transfer after about 30 seconds.
How Linear used this technique
Read what Linear changed and follow the original sources.
Bound stalled transfers and retry them
Linear replaced its checkout step with a composite action that retries with backoff, sets GIT_HTTP_LOW_SPEED_LIMIT and GIT_HTTP_LOW_SPEED_TIME so a stalled connection aborts after about 30 seconds, and uses a checkout cache that keeps a persistent git mirror on a sticky disk. The runner provider traced the hangs to intermittent degradation on its network link to GitHub.
- Use it when
- Checkout tail latency is repeatedly stalling a critical-path job.
- Before applying it
- Pair every abort with a retry, so a stalled transfer starts again. A persistent mirror is provider-specific.
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