Is there a way to avoid rebuilding and running the whole testsuite for changes that are outside the test scope ?
To save minutes for both saving quotas and the environment :)

Is there a way to avoid rebuilding and running the whole testsuite for changes that are outside the test scope ? To save minutes for both saving quotas and the environment :)

In principal: yes. I haven't looked into that yet, here. But in my daily shop I am accustomed to have the build be smart enough to not redo the work if there is nothing to do (and with builds running for hours that matters a lot).
I will add it as an todo with the testing.

Not sure what to think about the list of maintainers listed in https://repology.org/project/rmlint/information

Debian will need to remove this link while packaging for privacy reason.