chore(ci): raise stale bot operations-per-run cap - #3859
Merged
Conversation
|
😎 This pull request was merged. |
Contributor
|
Reviews (1): Last reviewed commit: "raise stale bot operations cap" | Re-trigger Greptile |
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
1 participant
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.
Problem
The stale workflow uses the actions/stale default of 30 operations per run. With ~120 open PRs it exhausts the budget on freshly-eligible PRs every run ("No more operations left! Exiting...") and never reaches long-idle ones like #2307, so they are never marked stale.
Changes
Set
operations-per-run: 300so each run can sweep the full PR backlog.How did you test this?
Confirmed the cap in the 2026-07-28 run log (31 operations, then early exit). Config-only change, next scheduled run exercises it.
Automatic notifications