From 619517aa29f6dfe3158205797767cbf2707a94fc Mon Sep 17 00:00:00 2001 From: Bishal Prasad Date: Sun, 11 Dec 2022 12:55:03 +0530 Subject: [PATCH] Update tips-and-workarounds.md --- tips-and-workarounds.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tips-and-workarounds.md b/tips-and-workarounds.md index ba0d27b..296747f 100644 --- a/tips-and-workarounds.md +++ b/tips-and-workarounds.md @@ -14,7 +14,7 @@ A cache today is immutable and cannot be updated. But some use cases require the restore-keys: | primes-${{ runner.os }} ``` - Please note that this will create a new cache on every run and hence will consume the cache [quota](#cache-limits). + Please note that this will create a new cache on every run and hence will consume the cache [quota](./README.md#cache-limits). ## 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. @@ -80,4 +80,4 @@ jobs: env: GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` - \ No newline at end of file +