Do you mean an option when using the Action (which is a field in action.yml) or passing a "configuration file" in YAML format to the Action?

Either?

Then, I would suggest rewriting the scripts in Python, instead of using bash. Manipulating YAML in bash and/or detecting a "polimorfic" argument is a pain in comparison.

@umarcor I was hoping it could just set a list of values to an environment variable?

Sure, the point is what content/syntax we allow:

uses: symbiflow/actions/checks@main
with:
  exclude: >
    a_pattern
    another_pattern

uses: symbiflow/actions/checks@main
with:
  exclude: |
    a_pattern
    another_pattern

uses: symbiflow/actions/checks@main
with:
  exclude: exclude_list.yml

In all cases, an envvar named INPUT_EXCLUDE will contain the value(s). In the first case, values are separated by spaces. In the second case, values are separated by newlines. In the last case, reading the YAML file would be required.

First two seem fine, I don't think we need the third one at the moment?

Single exclude pattern list for all tests or one for check_license and a different one for check_python?