-
-
Notifications
You must be signed in to change notification settings - Fork 91
Open
Description
Expected Behavior
If a PR has 2 check runs with the same name, and one fails and one succeeds, after they both finish
"#check-failure=1"should betrue"#check-success=1"should betrue
Actual Behavior
Tested with the Mergify config editor against a more complex PR that has been closed and merged, effectively the results are
"#check-failure=1"isfalse"#check-failure=0"istrue"#check-success=1"istrue
Steps to Reproduce the Problem
- Create two workflows (different files) with the same job name. One workflow always succeeds, one workflow always fails.
- Use a Mergify configuration with condition checking for zero pending, 1 failure, 1 success.
- See that the condition is never satisfied, because at the end of the runs,
"#check-failure=1"isfalse.
Specifications
More details in this discussion
Metadata
Metadata
Assignees
Labels
No labels