Skip to content

Commit 7216d26

Browse files
felixdivohardbyte
authored andcommitted
Fix the way CI status conditions are specified for Mergify
Apparently [our setup does not work](https://github.com/hardbyte/python-can/runs/4006357753). Instead, we should do it [like in this repo](https://github.com/Mergifyio/mergify-engine/blob/main/.mergify.yml#L14-L19).
1 parent 5ef230a commit 7216d26

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

.mergify.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
queue_rules:
22
- name: default
33
conditions:
4-
- "status-success=test,format" # "GitHub Actions works slightly differently [...], only the job name is used."
4+
- "status-success=test" # "GitHub Actions works slightly differently [...], only the job name is used."
5+
- "status-success=format"
56

67
pull_request_rules:
78
- name: Automatic merge passing PR on up to date branch with approving CR
@@ -10,7 +11,8 @@ pull_request_rules:
1011
- "#approved-reviews-by>=1"
1112
- "#review-requested=0"
1213
- "#changes-requested-reviews-by=0"
13-
- "status-success=test,format"
14+
- "status-success=test"
15+
- "status-success=format"
1416
- "label!=work-in-progress"
1517
actions:
1618
queue:

0 commit comments

Comments
 (0)