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
222
223
224
225
226
227
228
229
230
231
232
233
234
235
|
.common_conditions:
label_exemptions: &label_exemptions
forbidden_labels:
- technical debt
- Accepting Merge Requests
- backstage
- security
- customer
- customer+
- test
- development guidelines
- schema redesign
- direction
resource_rules:
issues:
rules:
- name: Mark stale issues with no milestone for closure
conditions:
date:
attribute: updated_at
condition: older_than
interval_type: months
interval: 12
milestone:
- No Milestone
state: opened
<<: *label_exemptions
actions:
labels:
- awaiting feedback
- auto updated
mention:
- markglenfletcher
comment: |
Hi,
First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.
This issue will be closed, as it meets the following criteria:
* No activity in the past 12 months
* No milestone (unscheduled)
We'd like to ask you to help us out and determine whether this issue should be reopened.
If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention.
If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.
Thanks for your help
- name: Mark stale issues for closure
conditions:
date:
attribute: updated_at
condition: older_than
interval_type: months
interval: 3
labels:
- No Label
state: opened
actions:
labels:
- awaiting feedback
- auto updated
mention:
- markglenfletcher
comment: |
Hi,
First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.
This issue will be closed, as it meets the following criteria:
* No activity in the past 3 months
* Unlabelled
We'd like to ask you to help us out and determine whether this issue should be reopened.
If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention.
If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.
Thanks for your help
- name: Close non-updated issues
conditions:
date:
attribute: updated_at
condition: older_than
interval_type: weeks
interval: 2
labels:
- awaiting feedback
- auto updated
<<: *label_exemptions
state: opened
actions:
labels:
- auto closed
mention:
- markglenfletcher
status: close
comment: |
Closing this issue down in accordance with our [Issue Triage Policies](https://gitlab.com/gitlab-org/triage). Please reopen the issue if you feel that the issue is still relevant. Thanks!
- name: Mark potentially interesting feature proposals
conditions:
labels:
- feature proposal
state: opened
upvotes:
attribute: upvotes
condition: greater_than
threshold: 10
milestone:
- No Milestone
actions:
labels:
- auto updated
- potential proposal
- name: Mark very popular, unscheduled feature proposals
conditions:
labels:
- feature proposal
state: opened
milestone:
- No Milestone
upvotes:
attribute: upvotes
condition: greater_than
threshold: 50
actions:
labels:
- auto updated
- popular proposal
- name: Mark stale bugs for closure
conditions:
date:
attribute: updated_at
condition: older_than
interval_type: months
interval: 6
labels:
- bug
milestone:
- No Milestone
state: opened
<<: *label_exemptions
actions:
labels:
- awaiting feedback
- auto updated
mention:
- markglenfletcher
comment: |
Hi,
First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.
This issue will be marked for closure, as it meets the following criteria:
* Issue is open
* No activity in the past 6 months
* Labelled as a bug
* Unscheduled (no milestone)
We'd like to ask you to help us out and determine whether this issue should be reopened.
Because this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or on GitLab.com, to help us to understand whether the bug still needs our attention.
Thanks for your help
- name: Mark stale Support Requests for closure
conditions:
date:
attribute: updated_at
condition: older_than
interval_type: months
interval: 3
labels:
- support request
milestone:
- No Milestone
state: opened
actions:
labels:
- awaiting feedback
- auto updated
mention:
- markglenfletcher
comment: |
Hi,
This issue was labelled as a support request.
This issue will be marked for closure, as it meets the following criteria:
* Issue is open
* No activity in the past 3 months
* Labelled as a support request
* Unscheduled (no milestone)
We'd like to ask you to help us out and determine whether this issue should remain open.
Please could you revisit the issue and provide an update if it is still relevant.
Thanks for your help
merge_requests:
rules:
- name: Encourage old Community Merge Requests to completion
conditions:
date:
attribute: updated_at
condition: older_than
interval_type: months
interval: 6
labels:
- Community Contribution
state: opened
actions:
labels:
- awaiting feedback
- auto updated
mention:
- rymai
comment: |
Hi,
First of all, thank you for creating a Merge Request to help improve the GitLab product. We are running through old Merge Requests and asking authors to update their Merge Requests
This Merge Request was chosen, as it meets the following criteria:
* Open
* Labelled ~"Community Contribution"
* No activity in the past 6 months
We'd like to ask you to help us out and let us know whether:
* You would like to continue the work here
* You would like us to take on the Merge Request for you
* You would like us to close down the Merge Request
Thanks for your help
|
