[SPARK-30173] Tweak stale PR message #27114
Closed
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
Contributor
Author
|
cc @dongjoon-hyun - Before merging this in, we may want to wait a bit to confirm that removing the Stale tag does indeed work as we expect. |
Member
|
I actually saw this and I think it works. |
HyukjinKwon
approved these changes
Jan 7, 2020
|
Test build #116213 has finished for PR 27114 at commit
|
Member
|
retest this please |
|
Test build #116225 has finished for PR 27114 at commit
|
srowen
approved these changes
Jan 7, 2020
Member
|
Merged to master |
Member
|
+1, late LGTM. Thank you, all! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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-on to #26877.
What changes were proposed in this pull request?
This PR tweaks the stale PR message to clarify the procedure for reopening a PR after it has been marked as stale.
Why are the changes needed?
This change should clarify the reopening process for contributors.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A