Closed LightAndLight closed 1 year ago
I noticed a cache miss (https://github.com/LightAndLight/ipso/actions/runs/4098584146/jobs/7067800203#step:15:20) even though the cache key existed:
I learned that caches aren't actually shared between branches: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache, so if a pull request creates a cache key, then a subsequent pull request can't access that key.
It seems that branches can access the cache keys of main, so this might mean I have to run the tests.yml workflow for main so that pull requests can use the cache properly:
main
tests.yml
on: push: branches: - main
I noticed a cache miss (https://github.com/LightAndLight/ipso/actions/runs/4098584146/jobs/7067800203#step:15:20) even though the cache key existed:![github-actions-caches](https://user-images.githubusercontent.com/2536121/216847650-c4a8b497-d15b-40f7-ae90-bfb4830a9a51.png)
I learned that caches aren't actually shared between branches: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache, so if a pull request creates a cache key, then a subsequent pull request can't access that key.
It seems that branches can access the cache keys of
main
, so this might mean I have to run thetests.yml
workflow formain
so that pull requests can use the cache properly: