action #122923
Updated by szarate over 1 year ago
Whenever a check fails in the CI, it's often difficult to find directly find the file that is causing the failure, for instance [here](https://github.com/os-autoinst/os-autoinst-distri-opensuse/actions/runs/3236875645/jobs/5303250915#step:6:2321). At the moment, moment things that come to mind are: 1. [Tidy checks](https://github.com/os-autoinst/os-autoinst-distri-opensuse/actions/runs/3236875645/jobs/5303250915#step:6:2321). checks](https://github.com/os-autoinst/os-autoinst-distri-opensuse/actions/runs/3236875645/jobs/5303250915#step:6:2321)s. 1. [Metadata checks](https://github.com/os-autoinst/os-autoinst-distri-opensuse/actions/runs/3883901788/jobs/6625750667#step:6:5799) #### Acceptance Criteria `Criteria 1. Passing checks done on files files, aren't shown unless `--verbose` or another flag is are passed during the calls to `make` See also: https://github.com/os-autoinst/os-autoinst/pull/2235 for silencing Tidy