-
Notifications
You must be signed in to change notification settings - Fork 426
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 stale config #757
add stale config #757
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #757 +/- ##
=======================================
Coverage 91.49% 91.49%
=======================================
Files 17 17
Lines 1622 1622
=======================================
Hits 1484 1484
Misses 138 138 |
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.
In general, I'm good with this bot being added. Let's make sure that the timeline makes sense for @MSeal.
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
maybe we can set even more relaxed delays, but I gues 1 year is long one :) |
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.
There are also 30 days for PR and 60 days for issues before anything practically happen (meaning being eventually closed) |
What does this PR do?
There are tens of idle issues so it would be good to have them resolved or closed as likely the issue was resolved but not reported back... but this is just a suggestion, would like to hear from you what you think 🐰