forked from DataDog/integrations-core
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathstale.yml
More file actions
33 lines (28 loc) · 1.37 KB
/
Copy pathstale.yml
File metadata and controls
33 lines (28 loc) · 1.37 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
# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
exemptLabels:
- changelog/Security
- kind/feature-request
- severity/critical
- severity/major
# Label to use when marking as stale
staleLabel: stale
# Comment to post when removing the stale label. Set to `false` to disable
unmarkComment: false
# Comment to post when closing a stale Issue or Pull Request. Set to `false` to disable
closeComment: false
pulls:
daysUntilStale: 30
daysUntilClose: 1095
markComment: >-
This pull request has been automatically marked as stale because it has not had activity
in the last 30 days. Note that this will not be automatically closed, but the notification
will remind us to investigate why there's been inactivity.
issues:
daysUntilStale: 30
daysUntilClose: 1095
markComment: |-
This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that this will not be automatically closed, but the notification will remind us to investigate why there's been inactivity.
If you would like this issue to remain open:
1. Verify that you can still reproduce the issue in the latest version of the integration.
1. Comment that the issue is still reproducible and include updated details if possible.
Thank you for participating in the Datadog open source community!