More friendly closing of commitfests #101
Merged
Conversation
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
JelteF
force-pushed
the
friendly-cf-close-handling
branch
from
f19044a to
d3f1fc7
Compare
JelteF
force-pushed
the
friendly-cf-close-handling
branch
from
d3f1fc7 to
e5f615b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
When a commitfest is closed authors currently need to move their patches. This
is an attempt to "age out" patches without interest automatically. This has a
few downsides though. For patches that have activity going on, this is just
busywork for the author. And currently it's not even very clear that authors
are expected to do this (i.e. it's only shown in the dashboard).
So this PR tries to improve the situation in three ways:
automatically