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
I am personally against stale bots. As it runs of predefined logic based on time factors, the content being closed is never subjected for any inspection, it can be an undue injustice to the code contributors.
Maybe we can customize the Probot to avoid closing issues that contains certain labels such as waiting-for-feedback or similar. Sounds like a great way to reduce number of old issues
Maybe we can customize the Probot to avoid closing issues that contains certain labels such as waiting-for-feedback or similar. Sounds like a great way to reduce number of old issues
I've been very happy with https://probot.github.io/apps/stale/.
After a set amount of time of inactivity on an issue or PR, the bot adds a label, such as stale. If there is still no activity after another set amount of time the issue is closed. You can also configure a label like pin to keep the bot from ever marking the issue/pr stale or closing it.
Here is the config we use on Nock.
I will say, that adding the bot to older repos does create a bit a churn initially that can be overwhelming.
I recommend rolling it out slowly on newer repos or ones with less open issues.
This repo has less than 30 open issues, it seems like a good candidate. A decision would have to be made on preferred timeframes before the bot takes action.
Activity
gireeshpunathil commentedon Mar 25, 2020
I am personally against stale bots. As it runs of predefined logic based on time factors, the content being closed is never subjected for any inspection, it can be an undue injustice to the code contributors.
UlisesGascon commentedon Apr 4, 2020
Maybe we can customize the Probot to avoid closing issues that contains certain labels such as
waiting-for-feedbackor similar. Sounds like a great way to reduce number of old issuesryhinchey commentedon Apr 4, 2020
Agree!
mastermatt commentedon Jun 4, 2020
I've been very happy with https://probot.github.io/apps/stale/.
After a set amount of time of inactivity on an issue or PR, the bot adds a label, such as
stale. If there is still no activity after another set amount of time the issue is closed. You can also configure a label likepinto keep the bot from ever marking the issue/pr stale or closing it.Here is the config we use on Nock.
I will say, that adding the bot to older repos does create a bit a churn initially that can be overwhelming.
I recommend rolling it out slowly on newer repos or ones with less open issues.
This repo has less than 30 open issues, it seems like a good candidate. A decision would have to be made on preferred timeframes before the bot takes action.
bjohansebas commentedon Jan 28, 2025
I think we've opted not to close issues with a bot, so we can close this