Closed
Conversation
Collaborator
|
Review requested:
|
Member
Author
|
CC @mhdawson Also this may need TSC approval? |
nodejs-github-bot
added
the
meta
Member
Author
|
(requesting your review as this modifies something that you gave some opinions on earlier) |
avivkeller
added
the
commit-queue-squash
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#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:
END_DATEto minimize disruption.END_DATEis down to 1 year, merge withclose-stale-pull-requests.yml.END_DATEreaches 6 months, merge withclose-stale-feature-requests.yml.