require-conditional-status-checks
require-conditional-status-checks copied to clipboard
blend
GitHub Action: Compose multiple (conditional) checks into a single check based on file paths in a pull request
I sometimes seen runs going from in_progress to unknown in the next run, or never changes from unknown in the first place. I have around 50 jobs in my yaml...
I know there are some usage examples in the README but it would be nice to have an actual example repo that we can fork and play with it to...
Right now I have a timeout of 15 minutes but since the job aren't being actually found (#12) it will stay like that until timeout:  It would be nice...
Right now if you have some tasks that run on `pull_request_target` they are not going to be picked up by the status checks: 
Does the `paths` options accept a negated wildcard path or is it necessary to add a `paths-ignore` option? Thank you BTW this is very useful 🙏🏽
Hi, Thanks for your action; it's pretty convenient in our monorepo environment. Some of our "checks" are in fact "statuses" (see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) POSTed to Github API by custom tools and...
