actions/cache
1
0
Fork 0
mirror of https://github.com/actions/cache.git synced 2024-09-20 05:21:38 +02:00
Code Issues Packages Projects Releases Wiki Activity

Removed verbose statements

Browse Source
This commit is contained in:
Sankalp Kotewar 2022-12-14 18:46:21 +00:00 committed by GitHub
parent 686bf424a8
commit 766d8255cd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
save/README.md
View File

@ -39,11 +39,9 @@ steps:
### Re-evaluate cache key while saving ### Re-evaluate cache key while saving
Some technologies like dot-net generate the lockfiles during the build time, due to which the already evaluated `${{ hashFiles('**/lockfiles') }}` hash doesn't match the actual hash. Using save action with the same key will not re-evaluate the key as the hash was generated during restores. However passing the expression to re-evaluate the hash would generate a new key in the save action now as save would be called after the build step. With save action, the key can now be re-evaluated while executing the action. This helps in cases where the lockfiles are generated during the build.
In other words, you can reuse the output of `restore` action in the input of the `save` action to input the same key. Otherwise, you can pass the hash logic for the key (ex. `${{ hashFiles('**/lockfiles') }}`) and let the save action re-evaluate the key just before executing. Let's say we have a restore step that computes key at runtime
Let's say we have a restore step that computes key at runtime.
``` ```
uses: actions/cache/restore@v3 uses: actions/cache/restore@v3