Linda_pp
Linda_pp
Okay, I'll try to implement it. I think the workaround should be as simple as possible so I'll simply try to insert the path separator. Once the implementation is done...
> Is that the desired behaviour? Oh, that's not the behaviour I expected.
The document says: > Specifies a key/value map of environment variables to set in the container environment. So this is only for container environment. Am I wrong?
The test on macOS failed but the failure seems not related to this PR's change: ``` Summary of all failing tests FAIL packages/http-client/__tests__/basics.test.ts (5.499 s) ● basics › does basic...
shellcheck doesn't seem to have configuration to list available environment variables. However it looks at the existing environment variables. Currently actionlint simply runs subprocesses inheriting its environment variables. So the...
@pbcahill You are mixing inputs for workflow call and inputs for action metadata. As @muzimuzhi said, `type` is not supported in action metadata. Please read the following document again. https://docs.github.com/en/actions/reference/workflows-and-actions/metadata-syntax#inputs...
Yeah, this should not be merged yet. I confirmed that `macos-13` was still available a few days ago.
Thanks for the reminder. The runner seems available yet but we should follow the official announcement. Merging.
Thanks for the heads up. However `actions/download-artifact@v3` is using `node16` runner and the runner is already dead. How does GHES use the action? Is `node16` still available on GHES server?
Previously `macos-11.0` actually existed. I don't know that `macos-12.0`, `macos-13.0`, ... are valid. Based on your experiment, I guess they are not (or no longer) valid though it is weird...