Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Branch-independent caches
See original GitHub issueThe issue template said
Issues should only be opened on if the issue relates to code in this repository.
which I don’t think is the case here. But it’s still relevant and I don’t know where else to file this.
I think caches should be accessible repository-wide, instead of being tied to a specific branch. The primary use case is caching external dependencies which can be shared between branches. If branch-specific caches are required one could include ${{ github.ref }} in the cache key (if slashes were handled properly that is, see #43).
Issue Analytics
- State:
- Created 4 years ago
- Reactions:12
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I 👍 this. The majority of our runs don’t get a cache hit due to this making
actions/cachemostly useless. I also think this should be mentioned in the README and Marketplace. I was pretty confused as to why none of my branches would get a cache hit despite the cache key being the same across runs.@vsvipul Ah that explains why I remembered that someone had commented, I’m subscribed to that one too. Thanks!