fix(stale): never auto-close — label only (days-before-close: -1)#25
Conversation
This universe never closes/dismisses/deletes an issue or PR — every request is preserved and evolved. Set the stale close window to -1 so the workflow labels but never closes; the 60-day informational `stale` label is unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Warning Review limit reached
Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Updates the repository’s scheduled stale triage workflow to preserve the informational stale label while ensuring issues/PRs are never automatically closed, aligning automation behavior with the repository doctrine.
Changes:
- Set
actions/staledays-before-closeto-1(never auto-close).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| stale-issue-message: 'Marked stale due to inactivity. Will close in 14 days.' | ||
| stale-pr-message: 'Marked stale due to inactivity. Will close in 14 days.' | ||
| days-before-stale: 60 | ||
| days-before-close: 14 | ||
| days-before-close: -1 |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5a1de605dc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| stale-pr-message: 'Marked stale due to inactivity. Will close in 14 days.' | ||
| days-before-stale: 60 | ||
| days-before-close: 14 | ||
| days-before-close: -1 |
There was a problem hiding this comment.
With days-before-close: -1, actions/stale@v10 no longer closes stale issues or PRs, but the stale messages still tell contributors the item “Will close in 14 days.” Every stale-label run will now post an inaccurate deadline, which contradicts the intended never-close policy and can mislead users into thinking their issue or PR is about to be closed.
Useful? React with 👍 / 👎.
The stale workflow auto-closed issues/PRs, violating this universe's absolute doctrine: we never close, dismiss, or delete — if it was ever asked for it was wanted.
This sets the close window to
-1(actions/stalenever-close), preserving the informationalstalelabel but never closing. Surgical, reversible, single-file.