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 Probot no-response configuration #18077

merged 1 commit into from Sep 20, 2018


None yet
3 participants

jasonrudolph commented Sep 20, 2018

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-needed label. 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 the more-information-needed label, 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


Possible Drawbacks

  • People may get upset that we're closing an issue. They may wrongly interpret it to mean that we don't care about the issue or that we refuse to address it. Hopefully the comment that the No Response app posts will help them understand that we do indeed want to help, but that we need more information in order to provide that help. 🤞
  • When we first install the app, its first "sweep" will identify about 20 issues that are more than 180 days old and have the more-information-needed label. 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


@jasonrudolph jasonrudolph requested a review from lee-dohm Sep 20, 2018


🌈 So wow 🌈


VSTS failure is a known flake on Windows, good to merge! Super excited to be getting some more Probot automation going

@jasonrudolph jasonrudolph merged commit a239b66 into master Sep 20, 2018

2 of 3 checks passed

Atom Pull Requests #20180920.1 failed
continuous-integration/appveyor/pr AppVeyor build succeeded
continuous-integration/travis-ci/pr The Travis CI build passed

@jasonrudolph jasonrudolph deleted the configure-probot-no-response branch Sep 20, 2018

This was referenced Sep 25, 2018

This was referenced Sep 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment