The charm-name is not really necessary for running quality checks, the charm-path is enough as each of the charm directories for both single and multi-charms repos have tox environments for each of the checks. This option will break v1 of this workflow, but will keep compatibility with v0 (and repositories that used main before introducing the charm-name input).
The charm-name is not really necessary for running quality checks, the charm-path is enough as each of the charm directories for both single and multi-charms repos have tox environments for each of the checks. This option will break v1 of this workflow, but will keep compatibility with v0 (and repositories that used main before introducing the
charm-nameinput).This change is being tested at https://github.com/canonical/kubeflow-dashboard-operator/pull/127