summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-merge-robot <k8s.production.user@gmail.com>2016-07-17 16:07:29 -0700
committerGitHub <noreply@github.com>2016-07-17 16:07:29 -0700
commitb375ca00fb2e9a0b9b1c430cca1133aa8bbda493 (patch)
tree69681a0c7524de85815530ab85f5dfe6c7b866c3
parentbfcd7225a5b8ea9eb717c416089d4538e2802ba9 (diff)
parent66a39c4518ad6b1e3390c39fcaedd112179cf6db (diff)
Merge pull request #29019 from apelisse/update-automation-doc-close-pr
Automatic merge from submit-queue Document auto-close on stale pull-request Document the change made by https://github.com/kubernetes/contrib/pull/891.
-rw-r--r--automation.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/automation.md b/automation.md
index 365bcdd9..a1f0144f 100644
--- a/automation.md
+++ b/automation.md
@@ -108,6 +108,18 @@ with numerous other functions. See the README in the link above.
Please feel free to unleash your creativity on this tool, send us new mungers
that you think will help support the Kubernetes development process.
+### Closing stale pull-requests
+
+Github Munger will close pull-requests that don't have human activity in the
+last 90 days. It will warn about this process 60 days before closing the
+pull-request, and warn again 30 days later. One way to prevent this from
+happening is to add the "keep-open" label on the pull-request.
+
+Feel free to re-open and maybe add the "keep-open" label if this happens to a
+valid pull-request. It may also be a good opportunity to get more attention by
+verifying that it is properly assigned and/or mention people that might be
+interested.
+
## PR builder
We also run a robotic PR builder that attempts to run tests for each PR.