This repository was archived by the owner on Mar 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17.3k
Add Probot no-response configuration #18077
Merged
Merged
Conversation
This file contains hidden or 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
lee-dohm
approved these changes
Sep 20, 2018
Contributor
lee-dohm
left a comment
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.
✨ 🌈 So wow 🌈 ✨
daviwil
approved these changes
Sep 20, 2018
Contributor
daviwil
left a comment
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.
VSTS failure is a known flake on Windows, good to merge! Super excited to be getting some more Probot automation going ✨
This was referenced Sep 25, 2018
This was referenced Sep 25, 2018
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.
Description of the Change
Add configuration in preparation for installing the No Response app on the atom/atom repository.
Currently, when someone opens an issue and we need additional information, a maintainer will ask the issue author for more information and the maintainer will apply the
more-information-neededlabel. In many cases, months (even years) can go by without the issue author responding to the request for more information. In these cases, because we still lack the requested information, the issue is not actionable. Today, a maintainer would need to manually search for issues with themore-information-neededlabel, identify ones that have been open for too long without a reply from the issue author, and then manually close those issues.To make more effective use of maintainers' time, and to help us more quickly distinguish actionable issues from non-actionable issues, we can use the No Response app to automate the manual process described above. 🤖✨
This pull request proposes that we start out with a fairly conservative configuration: If we've been waiting for a reply from the issue author for more than 180 days, and the issue author hasn't replied, the No Response app will close the issue and post a comment explaining why it's closing the issue.
Once we verify that this is working smoothly, I'd like to decrease the time window to something smaller than 180 days, perhaps 28 days. That change would take place in a follow-up pull request.
Alternate Designs
N/A
Possible Drawbacks
more-information-neededlabel. For anyone watching the atom/atom repository, or anyone subscribed to all of those issues, they'll receive a batch of notifications for all of those issues at once. 📨Verification Process
N/A