actions/cache
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge 62a3e42441b97f87b761cdd4091e283ad91e217f into 704facf57e6136b1bc63b828d79edcd491f0ee84

Browse Source
This commit is contained in:
Rik Huijzer 2023-09-08 16:41:32 +10:00 committed by GitHub
commit d32eadb01c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -60,7 +60,7 @@ If you are using a `self-hosted` Windows runner, `GNU tar` and `zstd` are requir
### Outputs
* `cache-hit` - A boolean value to indicate an exact match was found for the key.
* `cache-hit` - A boolean value to indicate an exact match was found for the key, or empty (not set) if no cache was restored.
> **Note** `cache-hit` will only be set to `true` when a cache hit occurs for the exact `key` match. For a partial key match via `restore-keys` or a cache miss, it will be set to `false`.

2
restore/README.md
View File

@ -14,7 +14,7 @@ The restore action restores a cache. It works similarly to the `cache` action ex
### Outputs
* `cache-hit` - A boolean value to indicate an exact match was found for the key.
* `cache-hit` - A boolean value to indicate an exact match was found for the key, or empty (not set) if no cache was restored.
* `cache-primary-key` - Cache primary key passed in the input to use in subsequent steps of the workflow.
* `cache-matched-key` - Key of the cache that was restored, it could either be the primary key on cache-hit or a partial/complete match of one of the restore keys.