Caching
How do I keep a Docker layer cache between pull requests?
Quick answer
Use a persistent remote builder — its cache is not scoped to a branch.
The detail that matters
GitHub's branch-scoped cache means every new PR starts cold, which is why Docker caching feels broken on PR-heavy repositories.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
Why does Cargo rebuild everything?Your cache key changes on every run, or target/ is not cached at all.Why is cache restore slow?GitHub throttles cache bandwidth, so a multi-gigabyte cache can take minutes to restore.How do I write a good cache key?Hash exactly the files that determine the cached content — usually the lockfile — and nothing else.What are restore-keys?Ordered prefixes tried when the exact cache key misses, so a partial match can still be restored.