This repository has been archived by the owner on May 9, 2024. It is now read-only.

No Response #21105

	name: No Response

	# What it does: Closes issues where the original author doesn't respond to a request for information.
	# 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:
	# Schedule for five minutes after the hour, every hour
	- cron: '5 * * * *'

	jobs:
	noResponse:
	runs-on: ubuntu-latest
	steps:
	- uses: lee-dohm/[email protected]
	with:
	token: ${{ github.token }}
	daysUntilClose: 14 # Number of days of inactivity before an Issue is closed for lack of response
	responseRequiredLabel: "reporter feedback" # Label indicating that a response from the original author is required
	closeComment: >
	This issue has been automatically closed because there has been no response
	to our request for more information. 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.

Provide feedback