ci(stale): bump operations-per-run to 1500 and add manual trigger#27037
Merged
ci(stale): bump operations-per-run to 1500 and add manual trigger#27037
Conversation
The stale workflow was hitting its 250 operations-per-run cap every daily run, causing the "No more operations left! Exiting..." warning and leaving a growing backlog of stale-labeled items that were never being closed. GitHub API headroom is plentiful (250 ops uses ~1.6% of the 15k/hour bucket), so raising to 1500 drains the backlog without any rate-limit risk. Also adds workflow_dispatch so maintainers can trigger the workflow from the Actions tab or via gh workflow run stale.yml. Signed-off-by: Ramon Roche <mrpollo@gmail.com>
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.
The stale workflow has been hitting its
operations-per-run: 250cap on every daily run, loggingNo more operations left! Exiting...before it finishes processing the candidate queue. Today's run (24223026205) processed 393 items, marked 39 new stale, but only closed 1 issue before exiting. There are currently 178 items carrying thestalelabel waiting to be closed, and the backlog is growing faster than the workflow can drain it.GitHub API headroom is not the constraint. After a full 250-op run the rate-remaining was 14,728/15,000, so 250 ops is about 1.6% of the hourly bucket. Bumping to 1500 uses ~10% and stays well under both the primary and secondary rate limits. The
actions/stalemaintainers explicitly recommend raising this when theNo more operations leftwarning appears.Also adds
workflow_dispatchso maintainers can trigger the workflow manually from the Actions tab or viagh workflow run stale.yml --repo PX4/PX4-Autopilot, which is useful for draining the backlog and for testing config changes without waiting for the next cron.Expect the first run after merge to be a catch-up run that closes more items than usual as it works through the accumulated stale-labeled backlog. Daily cadence should stabilize well under the new cap after that.