Repository navigation
chore: give pull requests a longer stale window in the shared stale workflow - #122
Merged
Merged
Conversation
shenxianpeng
changed the title
2bndy5
approved these changes
Oct 16, 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.
Before: the shared "Close stale issues" workflow treated pull requests like issues: marked stale after 60 days of inactivity and closed 7 days later.
After: issues keep the 60 + 7 day window. Pull requests are marked stale only after 180 days of inactivity and closed 30 days after that, with their own stale message.
How: set
days-before-pr-stale: 180,days-before-pr-close: 30andstale-pr-messageonactions/stale. Every caller already grantspull-requests: write. Prompted by CodeRabbit on cpp-linter/clang-tools-static-binaries#140.