summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorgrodrigues3 <grodrigues3@gmail.com>2017-07-24 21:13:27 -0700
committerGitHub <noreply@github.com>2017-07-24 21:13:27 -0700
commitc6d84454635b14f09b0b9a160db1e572e06af26b (patch)
tree43c0ff8920517d412f07fc4649c5990274740d99
parent5fd2e3609437729e6776d3916e7743acaf3fb82d (diff)
parent1ae8443028f0d40af846ae928a4a6d4bbb4e7b35 (diff)
Merge pull request #845 from xiangpengzhao/fix-prmd
Remove incorrect contents in pull-requests.md
-rw-r--r--contributors/devel/pull-requests.md6
1 files changed, 2 insertions, 4 deletions
diff --git a/contributors/devel/pull-requests.md b/contributors/devel/pull-requests.md
index e3c5abdd..8381ceca 100644
--- a/contributors/devel/pull-requests.md
+++ b/contributors/devel/pull-requests.md
@@ -13,8 +13,8 @@ This doc explains the process and best practices for submitting a PR to the [Kub
* [Comment Commands Reference](#comment-commands-reference)
* [Automation](#automation)
* [How the e2e Tests Work](#how-the-e2e-tests-work)
-- [Why was my PR closed?](#why-was-my-pr-closed-)
-- [Why is my PR not getting reviewed?](#why-is-my-pr-not-getting-reviewed-)
+- [Why was my PR closed?](#why-was-my-pr-closed)
+- [Why is my PR not getting reviewed?](#why-is-my-pr-not-getting-reviewed)
- [Best Practices for Faster Reviews](#best-practices-for-faster-reviews)
* [0. Familiarize yourself with project conventions](#0-familiarize-yourself-with-project-conventions)
* [1. Is the feature wanted? Make a Design Doc or Sketch PR](#1-is-the-feature-wanted--make-a-design-doc-or-sketch-pr)
@@ -158,8 +158,6 @@ The end-to-end tests will post the status results to the PR. If an e2e test fail
# Why was my PR closed?
-Pull requests that are purely support questions will be closed and redirected to [Stack Overflow](http://stackoverflow.com/questions/tagged/kubernetes). The Kubernetes developer community does this to consolidate questions into a single channel, improve efficiency in responding to requests, and make FAQs easier to find.
-
Pull requests older than 90 days will be closed. Exceptions can be made for PRs that have active review comments, or that are awaiting other dependent PRs. Closed pull requests are easy to recreate, and little work is lost by closing a pull request that subsequently needs to be reopened. We want to limit the total number of PRs in flight to:
* Maintain a clean project
* Remove old PRs that would be difficult to rebase as the underlying code has changed over time