Repository navigation
Conversation
actions/cache stops at the first matching restore prefix, so a leading build- key made lint, typecheck, and test always reuse the build cache and never their own saved task hashes.
|
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The narrow configuration change implements the intended cache priority while preserving fallback behavior.
Review effort: Balanced
Findings: None
What changed in this PR
Updates shared CI setup to prefer each job’s own Turbo cache.
Changes:
- Restores job-specific caches before the build cache, preserving existing fallbacks.
- Updates comments to explain restore-key precedence.
| File | Description |
|---|---|
.github/actions/setup/action.yml |
Reorders Turbo cache restore keys and clarifies comments. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Summary
${{ github.job }}ahead ofbuildin the Turbo cache restore-keys. actions/cache stops at the first prefix match, so the previous order made lint, typecheck, and test restore the Build cache on every run and never reuse the caches those jobs had saved.Note
Low Risk
CI caching configuration only; no application, auth, or data-path changes.
Overview
Reorders Turbo restore-keys in the shared setup action so each GitHub job (
lint,typecheck,test,build, etc.) matches its own prior.turbocache before falling back to the build job’s cache.Because
actions/cacheuses the first prefix match, putting build first caused non-build jobs to always restore the build cache and ignore caches they had saved on earlier runs. Comments in the action are updated to document that behavior.Reviewed by Cursor Bugbot for commit e6097b9. Bugbot is set up for automated code reviews on this repo. Configure here.