42 lines
1.6 KiB
YAML
42 lines
1.6 KiB
YAML
name: No Response
|
|
|
|
# **What it does**: Closes issues that don't have enough information to be
|
|
# actionable.
|
|
# **Why we have it**: To remove the need for maintainers to remember to check
|
|
# back on issues periodically to see if contributors have
|
|
# responded.
|
|
# **Who does it impact**: Everyone that works on docs or docs-internal.
|
|
|
|
on:
|
|
issue_comment:
|
|
types: [created]
|
|
|
|
schedule:
|
|
- cron: '20 * * * *' # Run each hour at 20 minutes past
|
|
|
|
permissions:
|
|
issues: write
|
|
pull-requests: write
|
|
|
|
jobs:
|
|
noResponse:
|
|
runs-on: ubuntu-latest
|
|
if: github.repository == 'github/docs'
|
|
steps:
|
|
- uses: actions/stale@184e7afe930f6b5c7ce52c4b3f087692c6e912f3
|
|
with:
|
|
repo-token: ${{ secrets.GITHUB_TOKEN }}
|
|
only-labels: 'more-information-needed'
|
|
days-before-stale: -1
|
|
days-before-issue-stale: 14
|
|
days-before-close: -1
|
|
days-before-issue-close: 0
|
|
close-issue-message: >
|
|
This issue has been automatically closed because there has been no response
|
|
to our request for more information from the original author. With only the
|
|
information that is currently in the issue, we don't have enough information
|
|
to take action. Please reach out if you have or find the answers we need so
|
|
that we can investigate further. See [this blog post on bug reports and the
|
|
importance of repro steps](https://www.lee-dohm.com/2015/01/04/writing-good-bug-reports/)
|
|
for more information about the kind of information that may be helpful.
|