Increase number of operations used by stale #26237
Merged
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.
Right now, our stalebot doesn't process all issues/pull requests. This is because by default, the stale action has a limit of 30 operations per run to avoid rate limiting. Since reading a batch of 100 issues/PRs is considered a single operation, we aren't able to fully make it through the backlog of issues/PRs (which is >4000). This applies even though we are only acting on PRs because GitHub can't effectively tell the difference between the 2.
Upping our limit to 100 will ensure that all pull requests will be processed. Since we only run this once per hour, this shouldn't really impact our rate limit of 1,000 operations per hour for the whole repo's GitHub Actions. We're not utilizing a significant portion of this elsewhere.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.