-
-
Notifications
You must be signed in to change notification settings - Fork 302
/
stale.yml
81 lines (63 loc) · 3.25 KB
/
stale.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
# Configuration for probot-stale - https://github.com/probot/stale
# Configuration options apply to both Issues and Pull Requests.
# We configure those individually to match our workflow (see `pulls:` and `issues:`)
pulls:
# Number of days of inactivity before a Pull Request becomes stale
daysUntilStale: 365
# Number of days of inactivity before a Pull Request with the stale label is closed.
# Set to false to disable. If disabled, Pull Request still need to be closed manually, but will remain marked as stale.
daysUntilClose: 21
# Comment to post when marking as stale. Set to `false` to disable
markComment: >
This pull request has been automatically marked as stale because it has not had recent activity.
Given the limited bandwidth of the team, it will be closed if no further activity occurs.
If you intend to work on this pull request, please reopen the PR.
Thank you for your contributions.
# Comment to post when closing a stale Pull Request.
closeComment: >
This pull request has been automatically closed due to inactivity.
If you are still interested in contributing this, please ensure that
it is rebased against the latest `master` branch, all review
comments have been addressed and the build is passing.
issues:
# Number of days of inactivity before a Pull Request becomes stale
daysUntilStale: 365
# Number of days of inactivity before an Issue with the stale label is closed.
# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
daysUntilClose: 21
# Comment to post when marking as stale. Set to `false` to disable
markComment: >
This issue has been automatically marked as stale because it has not had recent activity.
Given the limited bandwidth of the team, it will be automatically closed if no further
activity occurs.
If you feel this is something you could contribute, please have a look
at our [Contributor Guide](https://github.com/bndtools/bnd/blob/master/CONTRIBUTING.md).
Thank you for your contribution.
# Comment to post when closing a stale Issue.
closeComment: >
This issue has been automatically closed due to inactivity. If you can reproduce this on a
recent version of Bnd/Bndtools or if you have a good use case for this feature, please feel free
to reopen the issue with steps to reproduce, a quick explanation of your use case or a
high-quality pull request.
# Only issues or pull requests with all of these labels are check if stale. Defaults to `[]` (disabled)
#onlyLabels: []
# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
# exemptLabels:
# - pinned
# - security
# - "[Status] Maybe Later"
# Set to true to ignore issues in a project (defaults to false)
exemptProjects: true
# Set to true to ignore issues in a milestone (defaults to false)
exemptMilestones: true
# Set to true to ignore issues with an assignee (defaults to false)
#exemptAssignees: false
# Label to use when marking as stale
staleLabel: stale
# Comment to post when removing the stale label.
# unmarkComment: >
# Your comment here.
# Limit the number of actions per hour, from 1-30. Default is 30
limitPerRun: 30
# Limit to only `issues` or `pulls`
# only: issues