Allow using the cache for other than push and pull_request events
See original GitHub issueWhen triggering my action with on: ['deployment']
. It throws a warning about having no read permissions.
It doesn’t happen with on: push
.
##[debug]Resolved Keys:
##[debug]["Linux-yarn-...hash...","Linux-yarn-"]
##[debug]Cache Url: https://artifactcache.actions.githubusercontent.com/...hash.../
##[warning]No scopes with read permission were found on the request.
::set-output name=cache-hit,::false
Issue Analytics
- State:
- Created 4 years ago
- Reactions:37
- Comments:21 (4 by maintainers)
Top Results From Across the Web
Events that trigger workflows - GitHub Docs
You can use the github.event.issue.pull_request property in a conditional to take different action depending on whether the triggering object was an issue or ......
Read more >7 Github Actions Tricks I Wish I Knew Before I Started
#1: How to Use Github Action Triggers. The above code is pretty much self explanatory. The workflow will trigger on every pull request...
Read more >Using pull through cache rules - Amazon ECR
When pulling images using pull through cache, the Amazon ECR FIPS service ... ECR to create the repository for and push the cached...
Read more >Caching in GitLab CI/CD
Use cache for dependencies, like packages you download from the internet. Cache is stored where GitLab Runner is installed and uploaded to S3...
Read more >Easily explained: Differences between Push and Pull APIs
Even if you have only a pull API to play with, there are some neat tricks applications do to lessen their load, e.g....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The PR to allow all events to access cache is merged into
master
. It will be released as part of cache v2. We are targeting releasing v2 later this month.You can ping to
actions/cache@master
to preview this feature.repository_dispatch
would be really nice to have covered as well 😃