You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have raised this via a support request too, but I want to raise it here just in case:
The ci.sh script that is downloaded via curl and piped into sh will cause errors if sh is pointing to a strict POSIX-compliant shell like dash.
We've seen it throw errors like Error: stderr: sh: 81: [[: not found
Which shows that it doesn't support bash -style if blocks
A solution would be to add an input for the action, to specify which shell is piped the ci.sh script... But I'm not sure if that would work either, because:
Downloads the sh script
pipe to bash
bash interprets the shebang that points to #!/usr/bin/env sh
the env will return dash instead of bash in the end...
error remains...
The text was updated successfully, but these errors were encountered:
Hello !
I have raised this via a support request too, but I want to raise it here just in case:
The ci.sh script that is downloaded via
curl
and piped intosh
will cause errors ifsh
is pointing to a strict POSIX-compliant shell likedash
.We've seen it throw errors like
Error: stderr: sh: 81: [[: not found
Which shows that it doesn't support
bash
-style if blocksA solution would be to add an input for the action, to specify which shell is piped the
ci.sh
script... But I'm not sure if that would work either, because:#!/usr/bin/env sh
dash
instead ofbash
in the end...The text was updated successfully, but these errors were encountered: