-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@actions/exec doesn't support multiple commands #461
Comments
You can use which to get the full path to npm. |
I would expect |
@JasonEtco, AFAIK |
Sure enough, this works great
|
imo such design create big overhead when run multiple commands |
Is it big overhead though? I can't imagine any modern container/system would have a problem with this... :) |
You can use the above workaround to invoke a shell with your command and run it that way, if you need access to that. |
Describe the bug
Hello! I ran this script through
@actions/exec
:It was expanded and run:
So it looks like the first
npm
command was prefixed with/usr/local/bin
, but the second wasn't. It also didn't throw an error, which made this difficult to debug. What's the right way tocc JasonEtco/build-and-tag-action#4
To Reproduce
Create an action:
package.json:
The action:
Observe that the
build
command isn't properly run.Expected behavior
I'd expect the above command to "just work" - but if not, it should throw an error instead of fail silently.
The text was updated successfully, but these errors were encountered: