Automatically close “answered” issues if they have no activity for 30 days #9920
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… days. Often we have questions opened as issues that we have answered, but then there is no follow-up from the submitter. This enables us to indicate we have answered the question, and then the issue is scheduled to be closed after 30 days, presumably answered.
|
Thanks for making a pull request to JupyterLab! To try out this branch on binder, follow this link: |
|
Thanks! This should help (or close?) with this issue: #9714 |
Help, but probably not close. This doesn't take the hard line of closing any stale issue, just ones where we have explicitly indicated that we've triaged the issue as a user question (e.g., an installation issue, etc.) and tried to answer it. |
I did this. |
github-actions
bot
added
the
status:resolved-locked
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
References
Code changes
User-facing changes
Often we have questions opened as issues that we have answered, but then there is no follow-up from the submitter and the issue stays open. This enables us to explicitly indicate we have answered the question by giving the issue the
status:Answeredlabel, and then after 30 days of inactivity, the issue is scheduled to be closed after one more week, presumably answered.We could add a message before closure, but when we did that for the resolved-locked issues, it seemed to be mostly annoying without doing any good, so I opted for a silent scheduling, then closure a week later. The issue won't be locked for another 6 months of inactivity, so the submitter can always comment again and we can reopen it.
If this is merged, we'll need to create the labels
status:Answeredandstatus:Closing as Answered.Backwards-incompatible changes