-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Stalebot is being overly aggressive #2797
Comments
I'll look into it now |
It looks like it's a (seemingly uncommon) bug. In the meantime, we can:
Thoughts? |
While we're here - any other feedback / suggested config changes? We're down from ~530 to ~400 issues, and inspired a couple PRs along the way. There is some cost in swatting the marked issues though. |
I haven't seen this reoccur. Limited sample (though a handful of true negatives) |
In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here or remove the |
Thank you, slate-bot! I think we can let this one expire now 🤣 |
lol. I just re-logged-in a couple of days ago, since it seemed to have slept on us. Maybe the personal affront brought it back. |
E.g., see #1151 where stalebot closed an issue even after another comment.
Is this something we need to reconfigure or just a bug?
cc @pydata/xarray
The text was updated successfully, but these errors were encountered: