1+ # DSpace rules for flagging untouched issues and PRs as stale using 'stale':
2+ # https://github.com/actions/stale
3+ name : ' Mark issues and PRs as stale'
4+ on :
5+ # Schedule to run weekly on Sunday at 3:03am UTC
6+ # NOTE: This time is purposefully different from the "stale" bot settings in "DSpace/DSpace" to help
7+ # ensure we don't hit GitHub's rate limits.
8+ schedule :
9+ - cron : ' 3 3 * * 0'
10+
11+ permissions :
12+ issues : write
13+ pull-requests : write
14+
15+ jobs :
16+ stale :
17+ runs-on : ubuntu-latest
18+ steps :
19+ - uses : actions/stale@v10
20+ with :
21+ # Number of GitHub API calls to allow in a single run (to avoid hitting GitHub's rate limit)
22+ # Default is 30. But, we've found that only results in processing ~7 issues or PRs. So, we've increased it.
23+ operations-per-run : 60
24+ # Issues will be marked stale after 3 years of no activity
25+ days-before-issue-stale : 1095
26+ # Issues marked stale will be closed after one additional week of no activity
27+ days-before-issue-close : 7
28+ # High priority issues are never marked stale
29+ exempt-issue-labels : ' high priority'
30+ # When an issue is marked stale, this label and comment will be added to the issue.
31+ stale-issue-label : stale
32+ stale-issue-message : |
33+ This issue has been automatically marked as stale because it has not had
34+ activity in 3 years. It will be closed in 7 days if no further activity occurs.
35+
36+ Allowing issues to close as stale helps us filter out issues which can wait
37+ for future development time. All issues closed by this bot will continue to act
38+ like normal issues; they can be searched for, commented on or reopened at any point.
39+
40+ To extend the lifetime of an issue please comment below. This will help us to see
41+ that this issue is still affecting you with current versions of DSpace, and encourage
42+ us to re-prioritize this issue.
43+ # When an issue is closed, this comment will be added to the issue.
44+ close-issue-message : |
45+ This issue has been closed automatically as "stale". If this still affects you please
46+ request to re-open this issue via a comment, providing us with details on how this still
47+ impacts your usage of DSpace.
48+ # PRs will be marked stale after 1 year of no activity
49+ days-before-pr-stale : 365
50+ # PRs marked stale will be closed after two additional weeks of no activity
51+ days-before-pr-close : 14
52+ # High priority PRs are never marked stale
53+ exempt-pr-labels : ' high priority'
54+ # When a PR is marked stale, this label and comment will be added to the issue.
55+ stale-pr-label : stale
56+ stale-pr-message : |
57+ This pull request has been automatically marked as stale because it has not had
58+ activity in one year. It will be closed in 14 days if no further activity occurs.
59+
60+ Allowing pull requests to close as stale helps us filter out old work that is no longer
61+ relevant and helps developers focus on reviewing current work.
62+
63+ All pull requests closed by this bot act like normal pull requests;
64+ they can be searched for, commented on or reopened at any point.
65+
66+ If these changes are still relevant then please comment and/or rebase your PR based on the
67+ latest DSpace code. This will remove the stale status and notify us to assign a reviewer
68+ for your PR.
69+ close-pr-message : |
70+ This pull request has been closed automatically. If these changes are still relevant
71+ then please re-open this pull request with a comment and rebase your PR based on the latest
72+ DSpace code. This will notify us to assign a reviewer to your PR.
0 commit comments