actions/cache
1
0
Fork 0
mirror of https://code.forgejo.org/actions/cache.git synced 2025-05-19 06:14:46 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update documentation and licenses

Browse source 
Signed-off-by: Gregorio Litenstein <g.litenstein@gmail.com>
This commit is contained in:
Gregorio Litenstein 2023-01-31 11:24:37 -03:00
parent 203bc27916
commit 0417c21165
No known key found for this signature in database
GPG key ID: 4EB52A1A9CE2C63F
62 changed files with 1250 additions and 448 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.