Skip to content

Commit aca98ca

Browse files
authored
Update and rename no-response.yml to close-stale-issues.yml
1 parent 40561ba commit aca98ca

File tree

1 file changed

+18
-12
lines changed

1 file changed

+18
-12
lines changed
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,36 @@
1-
name: No Response
1+
name: 'Close stale issues'
22

33
# **What it does**: Closes issues where the original author doesn't respond to a request for information.
44
# **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.
65

76
on:
8-
issue_comment:
9-
types: [created]
107
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
1313

1414
jobs:
15-
noResponse:
15+
stale:
1616
runs-on: ubuntu-latest
1717
steps:
18-
- uses: lee-dohm/[email protected]
18+
- uses: actions/stale@v9
1919
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: >
2425
This issue has been automatically closed because there has been no response
2526
to our request for more information. With only the
2627
information that is currently in the issue, we don't have enough information
2728
to take action. Please reach out if you have or find the answers we need so
2829
that we can investigate further. See [this blog post on bug reports and the
2930
importance of repro steps](https://www.lee-dohm.com/2015/01/04/writing-good-bug-reports/)
3031
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

Comments
 (0)