Skip to content

I defined a ruleset requiring for a conditional check to pass for a PR to be merged, but it checks all PRs and blocks irrelevant PRs to the check #139540

Discussion options

You must be logged in to vote

This issue has been present in GitHub Actions for over two years. The official solution has changed several times, and the current recommendation is to avoid adding any past filter to the workflow. This means the job must be triggered unconditionally. Also, see this discussion.

A workaround to save compute resources is to use path filters in jobs or steps. If you detect that the change is unrelated to this CI, you can force the job to pass. Tools like path-filter or changed-files can help implement this approach.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@byungjoon72
Comment options

Answer selected by byungjoon72
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Actions Build, test, and automate your deployment pipeline with world-class CI/CD Question
2 participants