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
Stale bot is a bit aggressive #5520
Comments
I don't think it is too aggressive. 3 months without an update is usually means that the issue is not actionable. I would also like to know how much issues was closed but stale bot. I think they were not too much. I feel like stale bot force us to take a decision over those type of issues? Can we actionate it? Is clear enoght for any one to pick it up? We end up taking the decission of adding a tag to avoid the stealing (for example help wanting) or taking the decission to close the issue ourself before the 7 days period. And even if stale bot ends up closing an issue there is nothing preventing us to reopen the issue of we really think that it is worth it. |
I also though about this. The waiting for feedback issues should stale faster. |
Same. I actually believe the value it brings is net positive. I agree that some valuable issues might be closed, but so far it also helped us bring attention and solve issues that we forgot to follow up with.
Agree. I've sent this one here: |
Expected Behavior
Issues shouldn't always be auto closed just because they haven't been interacted with in a while.
Observed Behavior
Issues are marked for closure after 90 days, then closed a week later. Some valid issues are being closed, and it creates noise for anyone who left a comment or subscribed to updates.
Steps to Reproduce
Context
I think stale bot should only auto close:
Your Environment
--scan
option when running the gradle task):The text was updated successfully, but these errors were encountered: