-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add no-response workflow #6942
Add no-response workflow #6942
Conversation
I'd add |
It doesn't though? If you're referring to notifications, you get a notification even if the issue is only closed, so it doesn't matter much. If you're referring to actual pinging (á la |
Oh, then nevermind |
The run frequency should depend on how frequently the issue maintainers (mostly you) triage issues. If you do it every day, then the workflow should run every day or once in 2 days. This way, the max gap between you applying the label and the issue being closed would be 14-15 days. That is easily acceptable. Compare this to a frequency of 5 days. The issue might get closed 19-20 days later. |
Regardless of my triaging frequency, I think once per day is good enough. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me now.
Let's give it a try!
Odin: Unleash the Destroyer. |
What is it?
Description of the changes in your PR
Add a workflow to help manage issues where the author hasn't responded to requests for more information. Here's an example:
@opusforlife
creates a comment asking me for the missing enough and labels the issue aswaiting-for-author
I opened an issue on the action's repo asking whether this works with PRs, but there's no reply yet. In any case, usage with PRs right now should be avoided, as 14 days is a far too short span of time. I plan to modify the action so we can have a separate
daysUntilClose
for PRs, but for now, this should be used with issues only.I created a repo with an identical workflow to the one added in this PR. If anyone is interested in testing, feel free to ask and I'll send you an invite.
Due diligence