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
Use stale
bot/action to automate issue and PR lifecycle management?
#1142
Comments
I like the idea of "pinging authors", but I'm not a fan of "auto closing" issues/PRs. It makes me feel like the maintainers aren't doing their job... at least in cases where we're not waiting on the originator. And in those cases I think we need to manually see if who is on-the-hook for the next step. |
Luckily, our backlog isn't too bad. I think a large number of them are related to the new specs so I'm hoping we can revisit those issues soon since I think (at least) the discovery spec is becoming more real. |
Stale bot can be configured to only ping w/out closing if that helps. |
yep - I noticed that. I might try to set it up for the pinging stuff.... |
Closes: cloudevents#1142 Signed-off-by: Michael Gasch <15986659+embano1@users.noreply.github.com>
Done: #1144 |
Closes: cloudevents#1142 Signed-off-by: Michael Gasch <15986659+embano1@users.noreply.github.com>
Closes: cloudevents#1142 Signed-off-by: Michael Gasch <15986659+embano1@users.noreply.github.com>
Looking at the issues, and to some extent PRs, there's a lot of issues without activity/author feedback i.e. stale.
Should we add Github's
stale
action to automate the process of pinging authors, and eventually closing issues without activity/feedback?cc/ @clemensv @duglin
The text was updated successfully, but these errors were encountered: