Open thaJeztah opened 7 months ago
/cc @dvdksn @crazy-max @mat007 (maybe one of you knows where / how this is configured; this may not be a regular GitHub action; wondering if the stale-bot has a per-repository config file that can be used for filtering?)
Yes, we can do that. I’ll create a ticket!
thanks @mat007 and @thaJeztah
Thank you! ❤️
This has been changed and deployed now. Do we want to remove the lifecycle/frozen
label from e.g. #3282 to test it?
thanks @mat007! I removed lifecycle/frozen
on #3282, let's see if it works :-)
I think it looks good, right?
Yeah, I'm not sure it the auto-close kicks in only 30 days from when the label was removed, but if it turns out there's something amiss we can reopen this issue :)
thanks again @mat007
Yeah, I'm not sure it the auto-close kicks in only 30 days from when the label was removed
Ah that’s a good point, I never know if removing a label updates the issue or not. It probably does, indeed 😬
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
/lifecycle locked
I reopened this issue because I noticed that stale-bot just added the stale label to #3282.
Is this a docs issue?
Type of issue
Other
Description
The stale-bot automatically closes tickets after there's been no activity for some time. Some of these tickets were "acknowledged" (valid), but not yet being worked on.
While it's good to periodically clean up stale issues, we should also prevent tickets from being closed prematurely; (IMO) it's ok to have a backlog of tickets to work on; not all may have "top" priority, but having tickets to track things to improve is useful.
Location
Suggestion
We should prevent tickets from being closed automatically if;