mirror of
https://github.com/actions/cache.git
synced 2026-03-07 08:51:47 +08:00
Compare commits
2 Commits
40b3745dc1
...
9365bab5e5
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
9365bab5e5 | ||
|
|
25ee7a8ae9 |
@ -76,7 +76,7 @@ If you are using a `self-hosted` Windows runner, `GNU tar` and `zstd` are requir
|
||||
* `enableCrossOsArchive` - An optional boolean when enabled, allows Windows runners to save or restore caches that can be restored or saved respectively on other platforms. Default: `false`
|
||||
* `fail-on-cache-miss` - Fail the workflow if cache entry is not found. Default: `false`
|
||||
* `lookup-only` - If true, only checks if cache entry exists and skips download. Does not change save cache behavior. Default: `false`
|
||||
* `save-on-success` - If true, then the cache is written in the post action on success, or (if false) the cache will only be restored if available.
|
||||
* `save-on-success` - If true, then the cache is written in the post action on success, or (if false) the cache will only be restored if available. Default: `true`
|
||||
|
||||
#### Environment Variables
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ inputs:
|
||||
required: false
|
||||
deprecationMessage: |
|
||||
save-always does not work as intended and will be removed in a future release.
|
||||
If you only want to control whether a new cache will be written use `save-always` instead.
|
||||
If you only want to control whether a new cache will be written use `save-on-success` instead.
|
||||
Otherwise a separate `actions/cache/restore` step should be used instead.
|
||||
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
|
||||
outputs:
|
||||
|
||||
Loading…
Reference in New Issue
Block a user