forked from elastic/beats
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.mergify.yml
213 lines (212 loc) · 6.31 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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
queue_rules:
- name: default
conditions:
- check-success=beats-ci/pr-merge
pull_request_rules:
- name: self-assign PRs
conditions:
- -merged
- -closed
- "#assignee=0"
actions:
assign:
add_users:
- "{{ author }}"
- name: forward-port patches to main branch
conditions:
- merged
- label=forwardport-main
actions:
backport:
assignees:
- "{{ author }}"
branches:
- "main"
labels:
- "backport"
title: "[{{ destination_branch }}](backport #{{ number }}) {{ title }}"
- name: ask to resolve conflict
conditions:
- -merged
- -closed
- conflict
- -author=apmmachine
actions:
comment:
message: |
This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/
```
git fetch upstream
git checkout -b {{head}} upstream/{{head}}
git merge upstream/{{base}}
git push upstream {{head}}
```
- name: close automated pull requests with bump updates if any conflict
conditions:
- -merged
- -closed
- conflict
- author=apmmachine
- label=automation
actions:
close:
message: |
This pull request has been automatically closed by Mergify.
There are some other up-to-date pull requests.
- name: automatic approval for automated pull requests with bump updates
conditions:
- author=apmmachine
- check-success=beats-ci/pr-merge
- label=automation
- files~=^testing/environments/snapshot.*\.yml$
actions:
review:
type: APPROVE
message: Automatically approving mergify
- name: automatic squash and merge with success checks and the files matching the regex ^testing/environments/snapshot* are modified.
conditions:
- check-success=beats-ci/pr-merge
- label=automation
- files~=^testing/environments/snapshot.*\.yml$
- "#approved-reviews-by>=1"
actions:
queue:
method: squash
name: default
- name: delete upstream branch after merging changes on testing/environments/snapshot* or it's closed
conditions:
- or:
- merged
- closed
- and:
- label=automation
- head~=^update-stack-version
- files~=^testing/environments/snapshot.*\.yml$
actions:
delete_head_branch:
- name: delete upstream branch after merging changes on .go-version or it's closed
conditions:
- or:
- merged
- closed
- and:
- label=automation
- head~=^update-go-version
- files~=^\.go-version$
actions:
delete_head_branch:
- name: automatic approval for mergify pull requests with changes in bump-rules
conditions:
- author=mergify[bot]
- check-success=beats-ci/pr-merge
- label=automation
- files~=^\.mergify\.yml$
- head~=^add-backport-next.*
actions:
review:
type: APPROVE
message: Automatically approving mergify
- name: automatic squash and merge with success checks and the files matching the regex ^.mergify.yml is modified.
conditions:
- check-success=beats-ci/pr-merge
- label=automation
- files~=^\.mergify\.yml$
- head~=^add-backport-next.*
- "#approved-reviews-by>=1"
actions:
queue:
method: squash
name: default
- name: delete upstream branch with changes on ^.mergify.yml that has been merged or closed
conditions:
- or:
- merged
- closed
- and:
- label=automation
- head~=^add-backport-next.*
- files~=^\.mergify\.yml$
actions:
delete_head_branch:
- name: notify the backport policy
conditions:
- -label~=^backport
- base=main
- -merged
- -closed
actions:
comment:
message: |
This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @{{author}}? 🙏.
For such, you'll need to label your PR with:
* The upcoming major version of the Elastic Stack
* The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:
* `backport-v8./d.0` is the label to automatically backport to the `8./d` branch. `/d` is the digit
- name: notify the backport has not been merged yet
conditions:
- -merged
- -closed
- author=mergify[bot]
- "#check-success>0"
- schedule=Mon-Mon 06:00-10:00[Europe/Paris]
- "#assignee>=1"
actions:
comment:
message: |
This pull request has not been merged yet. Could you please review and merge it @{{ assignee | join(', @') }}? 🙏
- name: backport patches to 7.17 branch
conditions:
- merged
- label=backport-v7.17.0
actions:
backport:
assignees:
- "{{ author }}"
branches:
- "7.17"
labels:
- "backport"
title: "[{{ destination_branch }}](backport #{{ number }}) {{ title }}"
- name: backport patches to 8.3 branch
conditions:
- merged
- label=backport-v8.3.0
actions:
backport:
assignees:
- "{{ author }}"
branches:
- "8.3"
labels:
- "backport"
title: "[{{ destination_branch }}](backport #{{ number }}) {{ title }}"
- name: backport patches to 8.4 branch
conditions:
- merged
- label=backport-v8.4.0
actions:
backport:
assignees:
- "{{ author }}"
branches:
- "8.4"
labels:
- "backport"
title: "[{{ destination_branch }}](backport #{{ number }}) {{ title }}"
- name: backport patches to 8.5 branch
conditions:
- merged
- label=backport-v8.5.0
actions:
backport:
assignees:
- "{{ author }}"
branches:
- "8.5"
labels:
- "backport"
title: "[{{ destination_branch }}](backport #{{ number }}) {{ title }}"