Add a feature to automatically close issues as 'stale' when it hasn't been touched for > 4 months
gashcrumb opened this issue · 8 comments
Or however long, as issues that sit in the backlog long enough become totally irrelevant.
If it's necessary to keep a bug open, the issue reporter can always re-open, or the issue can be re-raised.
ok, let me pick that up. It will be a bit tricky, as the bot is only triggered on state changes (but not periodically which would be more appropriate for a cleanup job), but we can just from time to time check these when a webhook is triggered.
@syndesisio/all Before rolling out our own solution what do you think about using https://github.com/probot/stale for marking and closing old issues as stale ? Seems reasonably easy to install and configure.
Is four month as threshhold good enough ?
I like the idea of re-using something already written. And also, since we are doing housekeeping and tracking configs, deploy steps and secrets, this might be the best moment to track and document this!
ok, let me then jump on probot/stale.
I dont think we have to install anything, as its a running service.
Its just about coniguration.
Or should we install our own instance (to be 100% safe ?)
I created some issues at the beginning of November for clarifying the text in the UI. These issues are just being addressed now, after more than 4 months of no activity. To avoid automatic deletion, do I just need to add a comment so there is evidence of activity?
Yeah, so they won't be deleted, just closed automatically... so you're free to re-open etc.
If anything it's a good way to help keep important things from being completely forgotten.
I think we're doing this via a different bot, so I don't think we need to keep this open.