Bishal Prasad
Bishal Prasad
@laurentsimon while I completely agree to your assessment of the recurring effort needed to update the hash, any auto update of an action version can be a security hole for...
> What you describe only happens at first installation, so it's low risk. This is the way _everything_ works today: package managers do this: on first installation you must trust...
@varunsh-coder thanks for pointing out the gap in starter workflows! 🙇 I will add a point in the PR template to call this out. And please feel free to raise...
@1633605 Are you running multiple runners on same machine? Otherwise not sure how two workflows can use same file. If you really want to run two workflows concurrently, I would...
Persistent storage will have locking problem if multiple runners are trying to share it. To avoid it you may want to have cache directory inside `GITHUB_WORKSPACE` which is specific to...
> Given the current caching behavior, if you have a workflow file like the one below you will never be able to make use of caching: > ```yaml > name:...
@jelmd can you please share full logs for the step/job
Cache action does not use `/tmp` path directly nor does it restrict by doing such a check. However, the runner may not have access to `/tmp` and it is recommended...
@vsvipul please take a look