fix: preserve workspace cache across build checkout#6
Merged
Conversation
actions/checkout defaults to clean: true which runs git clean -ffdx, wiping any caller-restored build caches (e.g. .next/cache) before the build command runs. Setting clean: false lets callers restore a cache before invoking this action and have it survive to the build.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sets `clean: false` on the internal `actions/checkout` step in `build@v2`.
The default `clean: true` runs `git clean -ffdx` on every checkout, which wipes any build caches a caller restored into the workspace before invoking this action (e.g. `.next/cache`, `.turbo`, `.gradle`). Those caches are saved correctly at the end of the job but never actually read by the build — making caller-side caching a no-op.
Setting `clean: false` keeps a standard fetch + reset behaviour without nuking untracked/gitignored directories, so caller-restored caches survive to the build command.
This is a non-breaking change — callers that don't restore any cache are unaffected.
Test plan