Skip to content

meta: add old issue stalebot

Rodrigo Muino Tomonari requested to merge github/fork/RedYetiDev/patch-119 into main

#52712 was an overly aggressive update to the stalebot, which would've lead to mass notifications being sent out to users.

This PR is a much more restrained version of that update. If an issue is older than 4 years and hasn't been updated in over 5 months, it will be marked as stale. This approach is similar to #48051 but focused on issues rather than PRs.

The 4-year threshold was chosen because it applies to only 257 issues, which seems like a manageable starting point.

Over time, I think we can unify the stalebots with the following steps:

  • (This PR) Integrate non-feature request issues into the slower stalebot process.
  • Gradually reduce the END_DATE to minimize disruption.
  • Once the END_DATE is down to 1 year, merge with close-stale-pull-requests.yml.
  • Once the END_DATE reaches 6 months, merge with close-stale-feature-requests.yml.

Merge request reports