Actions/cache
1
Fork 0
mirror of https://github.com/actions/cache.git synced 2025-11-04 10:14:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix typo

Browse Source
This commit is contained in:
Matt Johnson-Pint 2022-11-21 08:47:17 -08:00
parent bdfce95e99
commit 1bd6a2275b
No known key found for this signature in database
GPG Key ID: FC13C394A988CF1D
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tips-and-workarounds.md
View File

@ -85,7 +85,7 @@ jobs:
#### Re-evaluating the cache key #### Re-evaluating the cache key
By default, the string resolved from the `key` parameter for restoring the cache will also be used for saving the cache. In some situations it may be preferred to re-evaluate the `key` parameter when saving, such as when part of the key's name is not available until after the restore has completed. In such cases, you can add the option `reevaluate-key: true`. By default, the string resolved from the `key` parameter for restoring the cache will also be used for saving the cache. In some situations it may be preferred to re-evaluate the `key` parameter when saving, such as when part of the key's name is not available until after the restore has completed. In such cases, you can add the option `reevaluate-key: true`.
For example, consider a a .NET solution that doesn't *normally* use `packages.lock.json` lock files. You may still want to generate a lock file for purposes of determining the cache key only. For example, consider a .NET solution that doesn't *normally* use `packages.lock.json` lock files. You may still want to generate a lock file for purposes of determining the cache key only.
```yaml ```yaml
- name: Cache Packages - name: Cache Packages