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
{{ message }}
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
For my own GitHub repos, I've configured the probot/stale bot to mark issues as stale after 90 days with no activity, and close after an additional 30 days if no further activity is found.
For the long-term maintenance of this collection, it might be nice to do the same thing here, just to make sure that 'rotting' issues and PRs (especially ones with no active interest) are automatically pruned.
Not sure the exact time we'd want to configure, but it's pretty easy to set up via the stale.yml configuration...
ISSUE TYPE
Feature Idea
COMPONENT NAME
Organization / maintenance
ADDITIONAL INFORMATION
N/A
The text was updated successfully, but these errors were encountered:
I agree. Let's establish this as soon as I finish cleaning up the backlog here.
tima
changed the title
Add Probot/stale bot to mark issues as stale and close after certain period?
Add Probot/stale bot to mark issues as stale and close after certain period
Aug 11, 2020
SUMMARY
For my own GitHub repos, I've configured the probot/stale bot to mark issues as stale after 90 days with no activity, and close after an additional 30 days if no further activity is found.
For the long-term maintenance of this collection, it might be nice to do the same thing here, just to make sure that 'rotting' issues and PRs (especially ones with no active interest) are automatically pruned.
Not sure the exact time we'd want to configure, but it's pretty easy to set up via the stale.yml configuration...
ISSUE TYPE
COMPONENT NAME
Organization / maintenance
ADDITIONAL INFORMATION
N/A
The text was updated successfully, but these errors were encountered: