Skip to content

Add automated stale issue triage

Nick Sellen requested to merge add-issue-triage into master

What does this MR do?

One issue we have is too many issues. This implements an "auto issue closing" bot to keep them cleaner (or remind people about old issues they might want to still deal with).

The assumption is that if the issue is important/useful somebody will update it, and if nobody does, that it is not very important.

At the moment (I think) I implemented the rules as follows:

  • any issues that have not had any activity on them for more than 8 months are labelled as "stale" and a comment is added to explain what that is about
  • any issues labelled "stale" that have not had activity within the last 2 weeks are closed and a comment added to explain why
  • a maximum of 1 issue is labelled/closed on each run - just to make sure it's working as intended and we don't suddenly close 200 issues :) - over time we can increase this number
  • the triage process would run once per night (controlled by the pipelines schedules)

How confident are you it won't break things if deployed?

Doesn't affect code. Potentially closes an issue you want open, you can just re-open it :)

Links to related issues

Checklist

  • added a test, or explain why one is not needed/possible... I tried it out locally with the dry run option
  • no unrelated changes
  • [not code] asked someone for a code review
  • joined #foodsharing-beta channel at https://slackin.yunity.org
  • [not code] added an entry to CHANGELOG.md (description, merge request link, username(s))

Merge request reports