Uh oh!
There was an error while loading. Please reload this page.
[BUILD] Close stale PRs - #16937
Closed
HyukjinKwon wants to merge 1 commit into
Closed
Conversation
HyukjinKwon
commented
Feb 15, 2017
MemberAuthor
cc @srowen. |
HyukjinKwon
commented
Feb 15, 2017
MemberAuthor
Please yell at me if any author of the PRs is active. I will definitely take it out. |
SparkQA
commented
Feb 15, 2017
Test build #72931 has finished for PR 16937 at commit
|
srowen
commented
Feb 15, 2017
Member
I am OK with closing these purely because they're inactive, and, it's trivial to reopen one if desired. PRs ought to reach a resolution rapidly. Ideally, if the resolution seems to be that the issue isn't an issue, or that the change shouldn't be made, also close the JIRA. If it's a plausible change and the PR just got orphaned, and the JIRA looks possibly relevant still at all, it can be left. |
zifeif2 pushed a commit
to zifeif2/spark
that referenced
this pull request
Nov 22, 2025
## What changes were proposed in this pull request? This PR proposes to close stale PRs. What I mean by "stale" here includes that there are some review comments by reviewers but the author looks inactive without any answer to them more than a month. I left some comments roughly a week ago to ping and the author looks still inactive in these PR below These below includes some PR suggested to be closed and a PR against another branch which seems obviously inappropriate. Given the comments in the last three PRs below, they are probably worth being taken over by anyone who is interested in it. Closesapache#7963Closesapache#8374Closesapache#11192Closesapache#11374Closesapache#11692Closesapache#12243Closesapache#12583Closesapache#12620Closesapache#12675Closesapache#12697Closesapache#12800Closesapache#13715Closesapache#14266Closesapache#15053Closesapache#15159Closesapache#15209Closesapache#15264Closesapache#15267Closesapache#15871Closesapache#15861Closesapache#16319Closesapache#16324Closesapache#16890Closesapache#12398Closesapache#12933Closesapache#14517 ## How was this patch tested? N/A Author: hyukjinkwon <gurwls223@gmail.com> Closesapache#16937 from HyukjinKwon/stale-prs-close.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What changes were proposed in this pull request?
This PR proposes to close stale PRs.
What I mean by "stale" here includes that there are some review comments by reviewers but the author looks inactive without any answer to them more than a month.
I left some comments roughly a week ago to ping and the author looks still inactive in these PR below
These below includes some PR suggested to be closed and a PR against another branch which seems obviously inappropriate.
Given the comments in the last three PRs below, they are probably worth being taken over by anyone who is interested in it.
Closes#7963
Closes#8374
Closes#11192
Closes#11374
Closes#11692
Closes#12243
Closes#12583
Closes#12620
Closes#12675
Closes#12697
Closes#12800
Closes#13715
Closes#14266
Closes#15053
Closes#15159
Closes#15209
Closes#15264
Closes#15267
Closes#15871
Closes#15861
Closes#16319
Closes#16324
Closes#16890
Closes#12398
Closes#12933
Closes#14517
How was this patch tested?
N/A