forked from nrfconnect/sdk-connectedhomeip
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.mergify.yml
More file actions
42 lines (42 loc) · 1.64 KB
/
.mergify.yml
File metadata and controls
42 lines (42 loc) · 1.64 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
pull_request_rules:
- name: Label conflicting pull requests
description: Add a label to a pull request with conflict to spot it easily
conditions:
- conflict
- '-closed'
actions:
label:
toggle:
- conflict
# WARNING: If the rule name below is changed, you must also update the
# condition `check-failure~=Automatic merge on PullApprove` to match the new name.
- name: Automatic merge on PullApprove
conditions:
- or:
- check-success=pullapprove
- label="fast track"
- '#approved-reviews-by>=1'
- '#review-threads-unresolved=0'
- '-draft'
- label!=docker
# Workaround for Mergify deadlock due to using "#check-failure=0":
# Mergify’s own action check can appear as failed/cancelled if conditions stop matching;
# and GitHub keeps those historic failures forever. Since `#check-failure=0` counts ALL
# failures (including historic ones), this would cause a deadlock and block merges indefinitely.
# We whitelist only this self-check so merges aren’t deadlocked, while all other failures still block.
- or:
- '#check-failure=0'
- and:
- '#check-failure=1'
# WARNING: This must match the rule name defined above.
# If the rule name changes, update this condition accordingly.
- check-failure~=Automatic merge on PullApprove
- '#check-pending=0'
- check-success~=Build
- or:
- check-success=pullapprove
- check-skipped=pullapprove
- check-neutral=pullapprove
actions:
merge:
method: squash