CI: Process more stale PRs, oldest first#31407
Merged
Merged
Conversation
Mariatta
approved these changes
Feb 18, 2022
Member
|
Thank you! |
Member
The bot started to process issues from 2017. I didn't know that default settings of actions/stale create such a bottleneck. |
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
6 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.
Follow up for python/core-workflow#93.
The GitHub Action to process stale PRs only runs on a subset of open PRs.
Let's run on more, and process the older ones first, they're more likely to be stale/abandoned.
More details: python/core-workflow#93 (comment)