Marco Ferrari

You have a point here, although I would classify this as an enhancement request. The main problem is that some tools expose some configuration variables only using command line options,...

By the way, this is one of the reasons why we switched to Bash arrays to dynamically compose commands. So maybe the solution is to provide something along those lines.

Makes sense. Let's see what we'd need to do first, then we can think if it's better to first document a workaround. And thanks for providing some examples. Those are...

`BASH_SEVERITY` and `MARKDOWN_CUSTOM_RULE_GLOBS` might work as they are, while `GITHUB_ACTIONS_COMMAND_ARGS` and `KUBERNETES_KUBECONFORM_OPTIONS` are likely impacted by this issue.

After checking a bit, I think this is actually a bug because we need additional processing after loading the environment variable where the options are stored. Adding it as it...

@detiber good suggestion. Moved your last request to #6086

> Error without using `grep -v`: > Run cat .github/super-linter.env .github/super-linter-default-validate.env >> "$GITHUB_ENV" > cat .github/super-linter.env .github/super-linter-default-validate.env >> "$GITHUB_ENV" > shell: /usr/bin/bash -e {0} > Error: Unable to process file...

#6085 should take care of this issue.

Hi @adhadse ! Do you mean [Ruff](https://github.com/astral-sh/ruff) ? If so, yes, it's already supported.

It runs Ruff with the following command: https://github.com/super-linter/super-linter/blob/c46346c7743f7ce191073a49d90a1fa7b3d11996/lib/functions/linterCommands.sh#L108 Is it what you're looking for, or something else?