Mark issues and PRs stale after 1 year inactivity + rate limit to 10 stale per week#6033
Merged
Conversation
prckent
changed the title
Contributor
Author
|
Test this please |
ye-luo
approved these changes
Jul 9, 2026
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.
Proposed changes
Reduce the stale threshold to 1 year.
Use the rate limiting so that no more than 10 actions will be taken each execution (currently weekly). Therefore, no-one will be snowed under by stale notifications and within a few months all the stale issues+prs will have been processed without the need to update this file.
What type(s) of changes does this code introduce?
Does this introduce a breaking change?
What systems has this change been tested on?
None
Checklist