summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com>2017-10-17 11:16:59 -0700
committerGitHub <noreply@github.com>2017-10-17 11:16:59 -0700
commit2005db9f9c67dfc4900f7c4293cdea60d720eeaa (patch)
treeb021976094a5d052b9d0238e6c91e19bc184a8b9
parentf06a102c3578b3572618e079fc3bf5b069c1c1d1 (diff)
parent60d5e0a567572d8d2862c3bf954eb5c1ef6a6650 (diff)
Merge pull request #1209 from porridge/merge-paragraphs
Automatic merge from submit-queue. Merge two paragraphs.
-rw-r--r--contributors/devel/automation.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/contributors/devel/automation.md b/contributors/devel/automation.md
index 0e250277..b3fddae1 100644
--- a/contributors/devel/automation.md
+++ b/contributors/devel/automation.md
@@ -35,10 +35,9 @@ The status of the submit-queue is [online.](http://submit-queue.k8s.io/)
### Ready to merge status
-The submit-queue lists what it believes are required on the [merge requirements tab](http://submit-queue.k8s.io/#/info) of the info page. That may be more up to date.
-
A PR is considered "ready for merging" by the submit queue if it matches the set
-of conditions listed in the merge requirements tab mentioned above.
+of conditions listed in the [merge requirements tab](http://submit-queue.k8s.io/#/info)
+of the info page.
Please visit that page for more details.
### Merge process