-
Notifications
You must be signed in to change notification settings - Fork 6k
Add no response action #29704
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 no response action #29704
Conversation
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.
This LGTM @adegeo
My only suggestion is to run it once a day, instead of every hour.
It's too bad that the action in lives in a private organization. Is there not something in the dotnet org we can use? |
@gewarren We can fork it and reference it? |
Co-authored-by: Bill Wagner <wiwagn@microsoft.com>
Hey @adegeo, @BillWagner, and @gewarren I'm curious, how exactly does this work? If someone posts an issue, and we don't touch it for 14 days - does it get closed? Ideally, that wouldn't be the case. How does it know when we engage, is that the |
Co-authored-by: Youssef Victor <youssefvictor00@gmail.com>
@IEvangelist The issue comment trigger is only used for detecting when the issue author actually responds after the "needs more info" label was added. The label is removed and if the issue was closed, it's reopened. |
Summary
I looked into the no response bot and it seems it's been deprecated for a year. They suggested using this action.
@gewarren
Do we need to add auth for this action in the github settings?
How do we remove the no-response bot app?