forked from galaxyproject/p4
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathconf.yaml
221 lines (220 loc) · 8.03 KB
/
conf.yaml
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
214
215
216
217
218
219
220
221
meta:
database_path: ./cache.sqlite
bot_user: galaxybot
repository:
owner: galaxyproject
name: galaxy
next_milestone: "16.07"
# List of people whose +1/-1 votes actually count
pr_approvers:
- martenson
- afgane
- bgruening
- blankenberg
- carlfeberhard
- dannon
- davebx
- erasche
- guerler
- jennaj
- jgoecks
- jmchilton
- jxtx
- natefoo
- nekrut
- nturaga
- nsoranzo
- tnabtaf
- mvdbeek
- remimarenco
# Filters are designed to say "is this PR at the current state in time interesting?"
filters:
-
# Name isn't really used except in logging messages.
name: Check Procedures PRs for mergability
# Conditions specify whether or not a given PR (and associated
# comments) are within certain ranges.
conditions:
# Note that these are technically an array of dictionaries with
# only one key. You can collapse these into a single dictionary
# if there aren't any duplicate keys, however the current
# design permits you to have multiple rules like
# `title_contains`
#
# We first find only open PRs
- state: 'open'
# If the title contains the text `[PROCEDURES]`
- title_contains: '[PROCEDURES]'
- title_contains__not: '[WIP]'
# And the PR is older than 168 hours ago
- created_at__ge: 'relative::168 hours ago'
# With 5 or more :+1: votes
- plus__ge: 5
# And ZERO :-1: votes
- minus__eq: 0
# If we pass all of our conditions, we execute one (or more)
# actions.
actions:
-
action: comment
comment: |
{author}'s PR has reached the threshold of 168 hours
and quorum of at least 5 binding +1 votes.
# The merge action is not yet implmemented, with no immediate
# plans
#-
#action: merge
#comment: "Automatically merged by Galaxy Jenkins Github Bot"
-
# And finally we have another rule for non-PROCEDURES PRs to
# non-dev branches, i.e. bugfixes to old branches.
# Unlike regular PRs to dev, these must have at least 2 :+1: votes.
name: Check bugfix PRs for mergability
conditions:
- state: 'open'
- title_contains__not: '[PROCEDURES]'
- title_contains__not: '[WIP]'
# Must have two people voting
- plus__ge: 2
# Bugfixes are not against dev
- to_branch__not: dev
actions:
-
action: comment
comment: |
{author}'s PR has reached the required number of votes
for merging.
# The following rules are loosely based on:
# https://github.com/galaxyproject/galaxy/blob/release_16.01/doc/source/project/issues.rst
-
name: Check merged PRs for missing kind tag.
conditions:
- state: 'merged'
# We're only tagging new PRs as of these changes
- created_at__ge: 'precise::2016-01-01'
- has_tag__not: 'merge'
- has_tag__not: 'kind/.*'
actions:
-
action: comment
comment: |
This PR was merged without a 'kind/' tag, please correct.
-
name: Add triage to new PRs.
conditions:
# We're only tagging new PRs as of these changes
- created_at__ge: 'precise::2016-01-01'
- state: 'open'
# This probably isn't perfect, but it'll be better
- has_tag__not: 'triage'
- has_tag__not: 'area/.*'
- has_tag__not: 'kind/.*'
- has_tag__not: 'status/.*'
- has_tag__not: 'merge'
actions:
-
action: assign_tag
action_value: 'triage'
-
name: Add status/WIP to new WIP PRs.
# Auto-tag things as WIP since submitters cannot.
conditions:
- created_at__ge: 'precise::2016-01-01'
- state: 'open'
- title_contains: 'WIP'
- has_tag__not: 'status/WIP'
actions:
-
action: assign_tag
action_value: 'status/WIP'
# Note that there is no corresponding "remove status/wip" action.
# Some devs don't use [WIP] in their title, so it wouldn't make sense
# to remove their manually added WIP
-
name: Add next milestone.
# We want to get code in soon, if a PR is ready, it should have a milestone set.
conditions:
- state: 'open'
# Exclude bugfixes / back patching
- to_branch: 'dev'
# Only complete PRs
- has_tag__not: 'status/WIP'
- has_tag__not: 'merge'
- created_at__ge: 'precise::2016-01-01'
- milestone: null
actions:
-
action: assign_next_milestone
-
name: Comment on missing milestones.
conditions:
- state: 'merged'
- created_at__ge: 'precise::2016-01-01'
- has_tag__not: 'merge'
- milestone: null
actions:
-
action: comment
comment: |
This PR was merged without a milestone attached.
-
name: Tag merges with missing merge tag
conditions:
- state: 'open'
- created_at__ge: 'precise::2016-01-01'
- title_contains: '[Merge]'
- has_tag__not: 'merge'
actions:
-
action: assign_tag
action_value: 'merge'
-
name: hotness - ouch
conditions:
- state: 'open'
# jmchilton originally requested this be more -1s than +1s.
- minus__ge: 3
- has_tag__not: 'popularity/unpopular'
actions:
-
action: assign_tag
action_value: 'popularity/unpopular'
-
name: hotness - mild
conditions:
- state: 'open'
- plus__ge: 1
- has_tag__not: 'popularity/low'
actions:
-
action: remove_tag
action_value: 'popularity/.*'
-
action: assign_tag
action_value: 'popularity/low'
-
name: hotness - medium
conditions:
- state: 'open'
- plus__ge: 4
- has_tag__not: 'popularity/medium'
actions:
-
action: remove_tag
action_value: 'popularity/.*'
-
action: assign_tag
action_value: 'popularity/medium'
-
name: hotness - spicy
conditions:
- state: 'open'
- plus__ge: 10
- has_tag__not: 'popularity/significant'
actions:
-
action: remove_tag
action_value: 'popularity/.*'
-
action: assign_tag
action_value: 'popularity/significant'