sergeysova / jq-action Goto Github PK

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

v2

Link to runnable example

No response

Steps to reproduce

I am using your workflow in an organisation workflow, and although it was running with no problem for a few months, today it started erroring out.

Expected behavior

The expected behaviour would be to set the $GITHUB_OUTPUT correctly.

Actual behavior

What is happening is erroring out:

Runtime

Other (please specify in steps to reproduce)

Package manager

No response

OS

No response

Build and bundle tools

No response

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Problem

Hi! Can feature of providing path to the .sh file instead of command itself be added?

Solution

  - name: Extract version from package.json
        uses: sergeysova/jq-action@v2
        with:
          cmdPath: 'scripts/cmd.sh'

Alternatives

can't think about

Hey,

Into cmd is it possible to use github input variables like :

- name: My cmd
  uses: sergeysova/jq-action@v2
  with:
    cmd: 'echo "version ${{ github.event.inputs.version }}"'

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Problem

It's a pity that this Action doesn't support Windows environment.

Solution

I am very sorry that I have limited ability to solve this problem independently.

Alternatives

I hope developers can solve this problem as soon as possible. Thank you very much.

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

v2

Link to runnable example

No response

Steps to reproduce

Create an action as explained on README.md

      - name: Extract version from package.json
        uses: sergeysova/jq-action@v2
        id: version
        if: ${{ inputs.push == true }}
        with:
          cmd: 'jq .version apps/${{ inputs.app }}/package.json -r'

Expected behavior

No warnings

Actual behavior

Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Runtime

Node v16

Package manager

yarn v2

OS

Linux

Build and bundle tools

Next.js

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

sergeysova/jq-action@v2

Link to runnable example

No response

Steps to reproduce

Create your .github workflow descriptor file and use this action:

uses: sergeysova/jq-action@v2
with:
  cmd: jq -n env

Expected behavior

After #9 being merged. The following error most NOT appear anymore at github action output logs:

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Actual behavior

It stills appear as tag v2 point to commit acfe8e3 instead of commit a3f0d4f

Runtime

No response

Package manager

No response

OS

No response

Build and bundle tools

No response

Hey there, thanks for the action. Would you be open to accepting a PR that adds support for multiline output? It's helpful for example when outputting one field from each item in a list. Right now, if the jq output has multiple lines, only the first line is set as the output, and the rest of the lines are just written to stdout.

It would look like this:

    - name: Extract contributed themes from package.json
      uses: .sergeysova/jq-action@v2
      id: themes
      with:
        cmd: 'jq .contributes.themes[].path ${{ inputs.working-directory }}/package.json --raw-output'
        multiline: true

And then the multiline output can be used like

    - name: Verify each contributed theme exists
      shell: bash
      run: |
        themes_in_package_json="${{ steps.themes.outputs.value }}"
        for theme in $themes_in_package_json; do
            ....
        done

Let me know! Thanks.