Note that this force-enables all lints, even those not part of rpmlint-factory-strict. That's kind of wrong (it differs from how this is run in OBS), on the other hand it's the only way to actually test that new tests for new lints actually work. We may actually want to have two CI jobs here, one that does enables all lints and one that runs with an unmodified configuration so that we see immediately that rpmlint-factory needs adjustment before a new test should be pushed to OBS.
This adds a CI like was suggested in openSUSE/rpmlint-checks#14 using Github Actions
Here is an example CI run: https://github.com/maltek/rpmlint-tests/runs/451150539?check_suite_focus=true
Note that this force-enables all lints, even those not part of
rpmlint-factory-strict. That's kind of wrong (it differs from how this is run in OBS), on the other hand it's the only way to actually test that new tests for new lints actually work. We may actually want to have two CI jobs here, one that does enables all lints and one that runs with an unmodified configuration so that we see immediately thatrpmlint-factoryneeds adjustment before a new test should be pushed to OBS.This also requires https://github.com/maltek/rpmlint-checks/commit/c6c1a037cc1d56f8fdb1a443468827629e2a7140 For whatever reason, this is currently fixed in rpm415-workaround.diff in OBS and not in our git repository...