Better control of which checks are required for a protected branch


We are using a monorepo and we have different status checks per component in our repo. We can’t require all the existing checks because if you only modify one component, you wouldn’t be able to merge a PR because GitHub would expect checks for other components to run and be successful.

What we need is a way of saying, *require all status checks* with the ability to exclude non-critical checks. Since we’re not able to do that, we have to maintain our own status that represents the combined status of all other statuses. We do that with a custom GitHub app that is subscribed to status/checks events.

When a new status/check event is published, we take the commit SHA and then “manually” combine the statuses of all other status and checks for that commit.

Hello @fredfaust

Thank you for your feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.

Once again, thank you for your input!

Greatly appreciated


I published an improved path-filter that works with required checks:

You may give it a try if this is still an issue.