Compare commits

...

2 Commits

Author SHA1 Message Date
Madison Swain-Bowden
5e9160c4db
Merge 830f24e4d8 into 668228422a 2026-03-18 08:35:38 -07:00
Madison Swain-Bowden
830f24e4d8
Fix cache re-evaluation key example in caching strategies docs
Based on the example provided, the save key here would always be different from the cache restore key. And on top of that, the function call for `hashFiles` looked incorrect on the save action (both in casing and for the files it was hashing).

This PR aligns the examples so they'd restore & save for the same purpose.
2026-02-04 11:51:19 -08:00

View File

@ -238,7 +238,7 @@ Case 2: Where the user would want to re-evaluate the key
```yaml
uses: actions/cache/save@v5
with:
key: npm-cache-${{hashfiles(package-lock.json)}}
key: cache-${{ hashFiles('**/lockfiles') }}
```
### Saving cache even if the build fails