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
As it currently stands, in order for an issue or PR to be marked as stale, the following conditions must be true:
(For issues)
The issue must be labeled feature request
The issue must not be labeled never-stale
The issue must have had no activity for 210 days, with a warning posted at day 180.
(For PRs)
The PR must not be labeled never-stale
The PR must be older than 525600 minutes (1 year)
The issue must have had no activity for 180 days, with a warning posted at day 150.
I propose we change this to cover more issues and pull requests, following this new configuration:
The issue or PR must not be labeled never-stale. If an issue, this also includes confirmed-bug.
The issue or PR must have no activity for 240 days, with a warning posted at day 210.
I understand this will likely incur a little bit of noise for the next run, but in the end, I think it'll help not just clean up the issue tracker, but draw attention to PRs that may have fallen through the cracks.
As it currently stands, in order for an issue or PR to be marked as stale, the following conditions must be true:
(For issues)
feature requestnever-stale(For PRs)
never-staleI propose we change this to cover more issues and pull requests, following this new configuration:
never-stale. If an issue, this also includesconfirmed-bug.I understand this will likely incur a little bit of noise for the next run, but in the end, I think it'll help not just clean up the issue tracker, but draw attention to PRs that may have fallen through the cracks.