Tighten stale issue and PR thresholds#54043
Conversation
Reduce the stale thresholds as a first step toward more aggressive cleanup: - Issues: 5 years → 4.5 years (1827 → 1644 days) - PRs: 6 months → 4 months (180 → 120 days) - Days before stale issue is closed: 30 → 14 days Plan to ratchet down further in ~1 month to 4 years and 2 months respectively. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adjusts the GitHub Actions stale workflow thresholds to label/close inactive issues and PRs sooner as part of a broader cleanup effort.
Changes:
- Reduce
days-before-issue-stalefrom ~5 years to ~4.5 years. - Reduce
days-before-issue-closefrom 30 days to 14 days (and update the stale issue message accordingly). - Reduce
days-before-pr-stalefrom 6 months to ~4 months.
It seems to me like you are choosing to slowly decrease the staleness window so that we don't blanket mark a ton of PRs/issues as stale all at once. That makes sense to me, but what is the end-goal for the issue/PR staleness windows? Or are we targeting a specific number of stale/non-stale issues and PRs? And is there a specific issue tracking the ratchet down of the values and the timeline? |
The plan is in the PR description: PlanThis is the first step in a gradual tightening. In approximately one month, we plan to ratchet these down further to 4 years for issues and 2 months for PRs. I will log an issue to track this. |
|
|
Merging ahead of PR validation since it doesn't cover the action. |
Summary
Reduce the stale thresholds as a first step toward more aggressive cleanup of inactive issues and PRs.
Changes
Plan
This is the first step in a gradual tightening. In approximately one month, we plan to ratchet these down further to 4 years for issues and 2 months for PRs.
Related to #54044.