actions/cache
3
0
Fork 0
mirror of https://code.forgejo.org/actions/cache.git synced 2025-12-02 11:39:09 +00:00
Code Activity

Merge 4043ab8d77 into 9fa7e61ec7

Browse source
This commit is contained in:
Gregorio Litenstein 2025-02-12 23:41:23 +00:00 • committed by GitHub
commit 755333eb16
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
82 changed files with 241030 additions and 163080 deletions
Download patch file Download diff file Expand all files Collapse all files

3
tips-and-workarounds.md
View file

@ -21,7 +21,8 @@ A cache today is immutable and cannot be updated. But some use cases require the
```
Please note that this will create a new cache on every run and hence will consume the cache [quota](./README.md#cache-limits).
* As a way to get around this limitation, the `refresh-cache` option exists. The way this works is, after matching a key and restoring a cache, it makes a request directly to the Github API and deletes the contents of that cache entry, then leaving said key free to be updated.
## Use cache across feature branches
Reusing cache across feature branches is not allowed today to provide cache [isolation](https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache). However if both feature branches are from the default branch, a good way to achieve this is to ensure that the default branch has a cache. This cache will then be consumable by both feature branches.