forked from risingwavelabs/risingwave
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.mergify.yml
52 lines (49 loc) · 1.6 KB
/
.mergify.yml
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
43
44
45
46
47
48
49
50
51
52
queue_rules:
- name: default
conditions:
- "check-success=buildkite/pull-request"
- "check-failure!=buildkite/docker"
- "check-success=task-list-completed"
- "label=mergify/can-merge"
pull_request_rules:
- name: Automatic merge on approval (high priority)
conditions:
- "base=main"
- "#approved-reviews-by>=1"
- "#changes-requested-reviews-by=0"
- "check-success=buildkite/pull-request"
- "check-failure!=buildkite/docker"
- "check-success=task-list-completed"
- "label=mergify/can-merge"
- "label=mergify/high-priority"
actions:
queue:
name: default
method: squash
priority: high
- name: Automatic merge on approval
conditions:
- "base=main"
- "#approved-reviews-by>=1"
- "#changes-requested-reviews-by=0"
- "check-success=buildkite/pull-request"
- "check-failure!=buildkite/docker"
- "check-success=task-list-completed"
- "label=mergify/can-merge"
actions:
queue:
name: default
method: squash
priority: medium
- name: Notify author on queue failure
conditions:
- "check-failure=Queue: Embarked in merge train"
actions:
comment:
message: >
Hey @{{ author }}, this pull request failed to merge and has been
dequeued from the merge train. If you believe your PR failed in
the merge train because of a flaky test, requeue it by commenting
with `@mergifyio requeue`.
More details can be found on the `Queue: Embarked in merge train`
check-run.