|
1 |
| -name: No Response |
| 1 | +name: 'Close stale issues' |
2 | 2 |
|
3 | 3 | # **What it does**: Closes issues where the original author doesn't respond to a request for information.
|
4 | 4 | # **Why we have it**: To remove the need for maintainers to remember to check back on issues periodically to see if contributors have responded.
|
5 |
| -# **Who does it impact**: Everyone that works on docs or docs-internal. |
6 | 5 |
|
7 | 6 | on:
|
8 |
| - issue_comment: |
9 |
| - types: [created] |
10 | 7 | schedule:
|
11 |
| - # Schedule for five minutes after the hour, every hour |
12 |
| - - cron: '5 * * * *' |
| 8 | + # Schedule for every day at 1:30am UTC |
| 9 | + - cron: '30 1 * * *' |
| 10 | + |
| 11 | +permissions: |
| 12 | + issues: write |
13 | 13 |
|
14 | 14 | jobs:
|
15 |
| - noResponse: |
| 15 | + stale: |
16 | 16 | runs-on: ubuntu-latest
|
17 | 17 | steps:
|
18 |
| - - uses: lee-dohm/[email protected] |
| 18 | + - uses: actions/stale@v9 |
19 | 19 | with:
|
20 |
| - token: ${{ github.token }} |
21 |
| - daysUntilClose: 14 # Number of days of inactivity before an Issue is closed for lack of response |
22 |
| - responseRequiredLabel: "reporter feedback" # Label indicating that a response from the original author is required |
23 |
| - closeComment: > |
| 20 | + days-before-stale: 7 |
| 21 | + days-before-close: 7 |
| 22 | + stale-issue-message: > |
| 23 | + It has been 7 days since more information was requested from you in this issue and we have not heard back. This issue is now marked as stale and will be closed in 7 days, but if you have more information to add then please comment and the issue will stay open. |
| 24 | + close-issue-message: > |
24 | 25 | This issue has been automatically closed because there has been no response
|
25 | 26 | to our request for more information. With only the
|
26 | 27 | information that is currently in the issue, we don't have enough information
|
27 | 28 | to take action. Please reach out if you have or find the answers we need so
|
28 | 29 | that we can investigate further. See [this blog post on bug reports and the
|
29 | 30 | importance of repro steps](https://www.lee-dohm.com/2015/01/04/writing-good-bug-reports/)
|
30 | 31 | for more information about the kind of information that may be helpful.
|
| 32 | + stale-issue-label: 'stale' |
| 33 | + close-issue-reason: 'not_planned' |
| 34 | + any-of-labels: 'reporter feedback' |
| 35 | + remove-stale-when-updated: true |
| 36 | + |
0 commit comments