Conversation
Gives issues and PRs more time before going stale, and more room to react once they do. Also mentions the never-stale label as an exemption option in the stale comment. Co-Authored-By: Claude <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Approved: no actionable findings.
What is this? | From workflow: PR Review
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
theletterf
approved these changes
Sep 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.
The stale bot now waits 180 days of inactivity before labeling issues and pull requests stale, and 21 days after that before closing them.
Affects: Automation
Prompt summary: Bump the stale bot's inactivity threshold from 90 to 180 days and its autoclose window from 14 to 21 days, then confirm the
never-staleexemption label actually exists on the repo, creating it if not.Why
90 days of inactivity marked an issue or pull request stale too soon, and 14 days to respond after that left little room to react before it closed. The stale comment also had no way to say "never mark this stale" —
never-stalewas already wired intoexempt-issue-labelsandexempt-pr-labels, but the label did not exist onelastic/docs-builder, so nobody could apply it.What
Stale and close thresholds
days-before-stalemoves from 90 to 180 in.github/workflows/stale.yml, anddays-before-closemoves from 14 to 21. An issue or pull request now needs twice as long to go stale, and gets a week longer to respond once it does.Stale comment text
stale-issue-messageandstale-pr-messagenow name thenever-stalelabel as a third way out, alongside removing thestalelabel or leaving a comment. Thenever-stalelabel is created on the repo so that option resolves to something real.Made with Cursor