actions/cache
1
0
Fork 0
mirror of https://gitea.com/actions/cache.git synced 2024-11-23 04:42:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update restore/README.md

Browse Source 
Co-authored-by: Bishal Prasad <bishal-pdmsft@github.com>
This commit is contained in:
Sankalp Kotewar 2022-12-15 00:06:56 +05:30 committed by GitHub
parent d5c949690c
commit c11ac6c2fe
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
restore/README.md
View File

@ -122,7 +122,7 @@ steps:
### Reusing primary key and restored key in the save action ### Reusing primary key and restored key in the save action
One of the limitation you might experience is passing the same input in both `actions/cache/restore` and `actions/cache/save` action. To avoid this, you can make use of the `outputs` from the restore action to reuse the same primary key and also the key of the cache that was restored. This way changing any key in the restore action will automatically reflect in the subsequent actions where the same input is being used. Usually you may want to use same `key` in both actions/cache/restore` and `actions/cache/save` action. To achieve this, use `outputs` from the restore action to reuse the same primary key (or the key of the cache that was restored).
### Using restore action outputs to make save action behave just like the cache action ### Using restore action outputs to make save action behave just like the cache action