Skip to content
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

trying out posix sh #14

Merged
merged 2 commits into from
Nov 15, 2024
Merged

trying out posix sh #14

merged 2 commits into from
Nov 15, 2024

Conversation

dcarbone
Copy link
Owner

No description provided.

@dcarbone dcarbone linked an issue Nov 15, 2024 that may be closed by this pull request
@dcarbone dcarbone merged commit ca81012 into main Nov 15, 2024
68 checks passed
@dcarbone dcarbone deleted the dcarbone/posixish branch November 15, 2024 01:38
@digitalkaoz
Copy link

@dcarbone sadly no:

Run dcarbone/install-jq-action@v3.0.0
  with:
    version: 1.7
    force: false

Run _jq_bin="$(which jq)"
  _jq_bin="$(which jq)"
  if [ -f "${_jq_bin}" ]; then
    echo "found=true" >> $GITHUB_OUTPUT
  else
    echo "found=false" >> $GITHUB_OUTPUT
  fi
  shell: bash +e {0}

OCI runtime exec failed: exec failed: unable to start container process: exec: "bash": executable file not found in $PATH: unknown
Error: Process completed with exit code 126.

@dcarbone
Copy link
Owner Author

Ahhh, the action itself. Ok.

@dcarbone
Copy link
Owner Author

@digitalkaoz alright, I've pushed a fix for this to main. Please give it a go! Apologies for not getting it quite right the first time 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bash not always available
2 participants