-
Notifications
You must be signed in to change notification settings - Fork 419
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
Use github stale
bot to close old inactive issues
#1681
Comments
Hehe, yes, as you have seen, I have been diving in to try and get back on top of things. Moving forwards, a way to stay on top would be appreciated. I agree - bug and enhancement are where I tend to park things for later and they shouldn't get deleted. Question/Waiting response mean its with the person who opened the issue, and it might be possible to be more aggressive with these - if someone is interested enough to create an issue but won't respond to further requests for info, I think we should close the issue after say a month, maybe 2, with an invitation to re-open if they ever get the info. If all of that can be automated it would be very welcome. Anything else, maybe close after 6 months of inactivity, again with an invitation to re-open. I should/will do a better job of tagging issues moving forwards. |
Ok just to summarize a plan:
|
Yes, perfect.
|
Can we add a label "pending_close" or something after the warning?
Message ID: ***@***.***>
|
By default it applies a label |
That works!
|
Is there an existing feature request for this?
Your feature request
There are quite a few issues that have been open for years, without a label associated and with seemingly no activity in the thread (for instance sorting by least-recently updated I get this #739).
Solution
I would like to propose this Github action that may help to tidy up old issues that do not have any recent activity.
bug
andenhancement
, since are useful to keep open until the bug is resolved or the feature request has been implemented)dry-run
mode, to make sure that the configuration is correct and no issue gets closed by accidentstale
, and if still there is no activity happens, it can automatically close them.The text was updated successfully, but these errors were encountered: