You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why. Stale bot is awful for open source repositories, as it creates a false understanding of what is open or closed.
From a maintainer's perspective, it does help us fight through noise and focus on essential issues. We don't lock them and it's very easy to open things that accidentally go stale. It's a tradeoff, but we've found it helpful.
Activity
jsjoeio commentedon Oct 11, 2021
What would the ideal api look like for you?
Something like that?^
zoeleu commentedon Dec 15, 2021
Yep, sorry for late reply. Got buried in my notifications.
stale commentedon Jun 13, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.
zoeleu commentedon Jun 14, 2022
Why. Stale bot is awful for open source repositories, as it creates a false understanding of what is open or closed.
Article on this: https://blog.benwinding.com/github-stale-bots/
TLDR: You are creating a false-sense of fewer issues. Duplicate issues will happen more often, and you're not fixing anything.
PS: I still think this is an essential API, not just for my personal use, but for companies that use and want to "brand" their editors.
sibidharan commentedon Aug 3, 2022
Much needed feature. It will be helpful if we are able to pass it in the command line.
jsjoeio commentedon Aug 3, 2022
From a maintainer's perspective, it does help us fight through noise and focus on essential issues. We don't lock them and it's very easy to open things that accidentally go stale. It's a tradeoff, but we've found it helpful.
tomqwpl commentedon Mar 24, 2023
Another vote for this feature.
wyz-c commentedon Apr 25, 2024
+1
surajrimal07 commentedon Jul 12, 2024
+1