-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Tweak stale bot's configs #6058
Conversation
Currently that translates to ~2015-07-20, of which there are 11 issues: https://github.com/rust-lang/cargo/issues?q=is%3Aopen+sort%3Aupdated-asc+updated%3A%3C2015-07-20
I've allowed "edits from maintainers" so feel free to push to my branch with amends - if you'd like. |
@bors: r+ I'm gonna go ahead and land this to get the updated configs in, but we can certainly continue to iterate on wording! |
📌 Commit 49e9e4a has been approved by |
Yep 💯 |
☀️ Test successful - status-appveyor, status-travis |
@@ -38,7 +31,7 @@ markComment: > | |||
acceptable! | |||
|
|||
closeComment: > | |||
As I didn't see any updates I'm going to close this due to being stale. | |||
As I didn't see any updates in 30 days I'm going to close this. | |||
Please see the previous comment for more information! |
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.
Maybe add something about when it would be appropriate to reopen (or whom to ping if the person reading the comment is not the original reporter)?
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.
Sure!
I think just commenting should be enough, as we have enough repo watchers.
In terms of "when" what were you thinking?
Refs #6035
r? @wycats