Feature request: Allow usage of .shellcheckrc about actionlint HOT 6 CLOSED

It's intentional. When you have ~/.shellcheckrc in your local, it affects actionlint behavior in your local (and it will behave differently on CI). Such side effect should be avoided as much as possible.

What do you need to configure by .shellcheckrc file?

from actionlint.

@rhysd I wanted to disable this one error SC2129. As you can see on screenshot it is a style suggestion and would be nice if I could not be forced to fix this if this is not real issue. In general would be nice to be able to configure instead of only disabling whole shellcheck. We plan to use .shellcheckrc in project directory so no real issue there if it is in GIT.

from actionlint.

Thank you for sharing your motivation. I'll consider how to meet the requirement.

from actionlint.

@piotrekkr It seems that passing arguments via SHELLCHECK_OPTS variable can be a solution for this.

SHELLCHECK_OPTS='-e SC2129' actionlint

(Related to #258)

from actionlint.

It's intentional. When you have ~/.shellcheckrc in your local, it affects actionlint behavior in your local (and it will behave differently on CI). Such side effect should be avoided as much as possible.

This clarifies a lot for me, coming from #258. At least for me, I would like actionlint to utilize the .shellcheckrc configuration I have for the project I'm running it against - I agree that it's undesirable to use ~/.shellcheckrc for the reason you point out.

While using the SHELLCHECK_OPTS environment variable is a viable workaround, perhaps a long term solution would be for actionlint to (perhaps optionally) use, if present, the .shellcheckrc file in the working directory where actionlint is invoked (or actionlint could even accept the location of the .shellcheckrc file as an argument). I don't think shellcheck currently supports this use case, but there is an open issue for it: koalaman/shellcheck#1879

The primary reason I think this would be a better solution is because it can help avoid duplication of the ShellCheck configuration, what do you think @rhysd?

from actionlint.

@rhysd Yeah this could work if we did not use devops-actions/actionlint for linting.

  run-actionlint:
    name: Run actionlint
    runs-on: ubuntu-22.04
    timeout-minutes: 3
    steps:
      - name: Checkout app code
        uses: actions/checkout@v4
        with:
          persist-credentials: false
          show-progress: false

      - name: Run actionlint
        uses: devops-actions/[email protected]

It is wrapper around this tool. There seems to be no way to pass this env there. I'll create ticket in their repo about adding this somehow (maybe as input or to just pass env to docker). Anyway, thanks for your help. Will close this one.

from actionlint.