Skip to content
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

x/build/cmd/gopherbot: consider having WaitingForInfo check for the last comment instead of time applied #39796

Open
stamblerre opened this issue Jun 24, 2020 · 1 comment

Comments

@stamblerre
Copy link
Contributor

@stamblerre stamblerre commented Jun 24, 2020

In my experience, I often forget to apply WaitingForInfo to an issue, but the last response for the reporter has been weeks ago. When I come back to it and do apply it, I still have to wait another month for the issue to be automatically closed.

Would it make more sense for WaitingForInfo to check for the last comment? I believe the vscode bot checks for the last comment from a maintainer - maybe we could check for the last comment from an "unknown GitHub person"?

@gopherbot gopherbot added this to the Unreleased milestone Jun 24, 2020
@stamblerre stamblerre changed the title x/build/cmd/gopherbot: x/build/cmd/gopherbot: consider having WaitingForInfo check for the last comment instead of time applied Jun 24, 2020
@cagedmantis
Copy link
Contributor

@cagedmantis cagedmantis commented Jun 24, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants