sort issues by update instead of creation date #1157
Conversation
This file contains 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
|
yeah, this sorts by ascending or descending creation date (issue/pr number basically). The intent of the PR is to sort by update date instead. |
|
@MaksimZhukov @IvanZosimov what do you think of this change ? |
|
@HarithaVattikuti @priyagupta108 what do you think of this change ? |
ericLemanissier
force-pushed
the
patch-1
branch
from
7dcfdab to
51cbfc8
Compare
|
CI results available on https://github.com/ericLemanissier/stale/pull/22/checks |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Description:
When processing a limited number of issues/pull requests, it is more efficient to process the ones with the older update first, because they are the ones with the highest chance of being stale.
Check list: