Load a schema snapshot without abandoning migration tests

Linear’s API containers load a generated schema snapshot and bootstrap file when a pull request leaves the schema unchanged.

View in Markdown

Prompt

Evaluate and apply this CI technique to my repository: Load a schema snapshot without abandoning migration tests.

Linear’s API containers load a generated schema snapshot and bootstrap file when a pull request leaves the schema unchanged.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/schema-snapshots.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How Linear used this technique

Read what Linear changed and follow the original sources.

Load a schema snapshot without abandoning migration tests

Linear’s API containers load a generated schema snapshot and bootstrap file when a pull request leaves the schema unchanged, which cut database setup from roughly 12 seconds to 1-2 seconds per container.

Use it when: Database initialization repeats the same migration history and consumes a material setup share.
Before applying it: Keep a required end-to-end migration replay, regenerate snapshots at the migration head and detect stale schema or seed state.

How Linear used this technique

Load a schema snapshot without abandoning migration tests

Company Playbooks

Related guides

Cut repeated setup and teardown from your test suite