CI cache blowout fix: write cache only on pushes to main, restore-only on PRs
DanielLockyer · x · 2026-11-04
Daniel Lockyer describes a common CI problem: caching on every build of every PR blows through default cache limits (10-25GB), platforms start LRU-evicting, and most workflows end up running with no cache at all.
His proposed fix: only store cache on pushes to main, and make PR builds restore-only. This keeps the cache pool from being evicted and lets PRs reliably hit warm caches.
Related event: Developer Warns Common CI Cache Antipattern Blows Storage Limits(2 posts)→
More from coding & agent
- 16x Microsoft MVP demos document extraction workflow with Cloudflare's Clairic model — dfinke · 2026-11-04
- GPT-6 Astra tool calls fail on Chat Completions; Responses API fixes them in Spring AI — therealdanvega · 2026-11-04
- Cloning a 1407-image costume site to Chinese with one AI workflow, from draft to delivery — songguoxiansen · 2026-11-04
- Dev open-sources AgentSnow, a minimal coding agent built to demystify Claude Code — damnGruz · 2026-11-04
- Pydantic AI adds Claude Code-style coding tools in one line, countering migration claims — samuelcolvin · 2026-11-04
- Horizon: open-source AI news radar with 12k stars generates daily bilingual briefings — Thysrael · 2026-11-04