Compare commits

...

2 Commits

Author SHA1 Message Date
Rik Huijzer
563b76ecfd
Merge 62a3e42441 into 0c45773b62 2024-03-19 20:15:20 +01:00
rikhuijzer
62a3e42441 Mention empty possibility for outputs.cache-hit 2023-04-24 09:20:22 +02:00
2 changed files with 2 additions and 2 deletions

View File

@ -65,7 +65,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`.

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.