Setting up CI checks people do not switch off
Every disabled check was once a good idea that fired at the wrong time. Reliability matters more than strictness.
A check that fails for reasons the author cannot act on gets skipped, then ignored, then deleted. The order is always the same and it takes about six weeks.
- Fail on things the author changed, never on things that drifted.
- Print the fix in the failure message. Nobody reads the wiki page you linked.
- Warn for a fortnight before you enforce, so people meet it while it is harmless.
Measure the skip rate
If a check is being bypassed more than once a fortnight, the check is wrong, not the team.