Rob Cowsill

I've been testing podman locally and it doesn't appear to be fully compatible with the docker CLI: - `podman save` requires an extra flag `-m` to permit saving multiple images...

This is a bit confusing; this action doesn't use [actions/cache](https://github.com/actions/cache) (an action), instead it uses [@actions/cache](https://github.com/actions/toolkit/tree/main/packages/cache) (a package on npm). The `actions/cache@v2` action uses the package `@actions/[email protected]` internally. That's the...

> Having the same issue here when using with: > > ``` > `on: > release: > types: > - released > - prereleased` > ``` Can you share workflow...

Would be good to have this as well as the option to force a cache update (#342)

> > What's up with package-lock.json having so many changes? > > I think this is because `package.json` specifies the versions with `^`, such as `^1.0.5`, which I believe means...

@dhadka Small edit to your first example to add multiple restore keys: ``` - uses: actions/cache-restore@v2 path: foo/ restore-keys: | ${{ runner.os }}-foo-${{ hashFiles('**/package-lock.json') }} ${{ runner.os }}-foo- - ......

I'm getting this too, on a GitHub-hosted runner. Logs are here: https://github.com/rcowsill/NodeGoat/runs/1504051837 (see the `Post Use cache (docker layers)` section) In my case it's happening when the cache with the...

It'd be great to have an option to specify the root path to use for the artifacts. It could be optional, and if not specified the current behaviour would be...

Another stopgap that might be useful is providing direct access to a file if it's the only one in the artifact.