Keep recent repositories in the same order when filtering #10380
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.
Fixes (no prior issue created)
I've taken a look at PR where this feature was introduced and haven't found anything which would support reversal during filtering. It seems this behavior was introduced by accident.
The effect is especially visible when using a filter which matches all of the repos, such as
\
Proposed changes
Screenshots
Before
No filter (GE repo comes first)
With filter (GE repo comes last)
After
With filter (GE repo comes first)
Test methodology
Merge strategy
I agree that the maintainer squash merge this PR (if the commit message is clear).
✒️ I contribute this code under The Developer Certificate of Origin.