Restore the NuGet cache without a post-save step in local-regtest - #76
Merged
Merged
Conversation
The cache action's post step re-hashes every csproj at the end of the job, when e2e/ holds root-owned files the containers wrote, and fails even with a !e2e/** exclusion (the walker descends before filtering). ci.yml saves this exact key on every push and PR, so this job only needs the restore entry point. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
Two green runs of
local-regtest.ymlon main carried a failedPost Cache NuGet packagesstep: the cache action re-evaluateshashFilesat the end of the job, whene2e/holds root-owned files the fixture's containers wrote, and the walk fails even with a!e2e/**exclusion (it descends before filtering). This job never needs to save the cache — ci.yml writes the same key on every push and PR — so it now usesactions/cache/restore, same pinned SHA, same key.🤖 Generated with Claude Code