Hm, that is unfortunate. Problem with you approach is that the PR is marked as “not completed yet (yellow dot)” or failed forever, although that is not the case. I guess I’ll remove the branch protection rules in that case. Thanks for your input.

Yes this is a real shame.

I’d like a “all tests run must pass” option, rather than a “these tests must run and pass (even though some of them may not be automatically started nor be relevant)” option.

any new update on this?

@pmeier @ayushxx7 You could try this workaround:

• put all those checks inside one workflow file
• DO NOT define paths: for pull request event
• create some initial job (e.g. init-job) that will decide what actual checks should run and which one should be skipped (based on changed paths) and set results as job output parameters
  • you can use this paths-changes-filter action to check what changed
• define each check so it will depend on init job (needs: init-job) and will only be run when output of init-job is set to correct value, e.g. if: needs.init-job.outputs.run_check1 == 'yes'

This way some check will run, and the rest will be skipped if path were not changed. GitHub treats skipped jobs as non blocking for PR merge so this should work fine I think.