2026-03-25

Check ignore rules

Pro users can now exclude individual checks from scoring — so repos aren't penalised for checks that simply don't apply to them.

Not every check applies to every team. If your org intentionally ships without a CONTRIBUTING guide, or you've made a deliberate decision not to use CODEOWNERS, a failing check isn't a problem — it's noise. Until now, those checks still dragged down your score.

That changes today. Pro users can now ignore individual checks in settings, removing them from scoring entirely.

How it works

In your settings, you'll find a new Check ignore rules section with a checkbox for each of the 12 checks. Uncheck any check you'd like to exclude. The remaining checks are re-weighted automatically, so ignored checks don't leave a gap — the score still reflects 100 points across whatever checks are active.

What it's for

The most common use case is suppressing checks that don't fit your workflow. For example:

  • Small teams that don't use CODEOWNERS or CONTRIBUTING files
  • Internal tooling repos where stale PR warnings are irrelevant
  • Monorepos where individual repo checks don't map cleanly to your structure

The goal is a score that reflects your actual standards — not a penalty for things you've consciously chosen not to do.

Pro only

Check ignore rules are available on the Pro plan. Upgrade to configure them.