summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/committing-code.txt
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2018-01-15 21:37:54 -0500
committerTim Graham <timograham@gmail.com>2018-01-17 08:48:53 -0500
commitb902878fd61feb83159a4770ccf327d532963b67 (patch)
tree4e5b6fa36d5dd7c192c595e3bfe9a0a6fdcb8b82 /docs/internals/contributing/committing-code.txt
parent196c257a230bba8f2f1b2021c383eb2744e8df41 (diff)
Doc'd the latest state of the Jenkins pull request builders.
Diffstat (limited to 'docs/internals/contributing/committing-code.txt')
-rw-r--r--docs/internals/contributing/committing-code.txt8
1 files changed, 3 insertions, 5 deletions
diff --git a/docs/internals/contributing/committing-code.txt b/docs/internals/contributing/committing-code.txt
index 4ce8576702..a56bf48281 100644
--- a/docs/internals/contributing/committing-code.txt
+++ b/docs/internals/contributing/committing-code.txt
@@ -20,11 +20,9 @@ best pull requests possible. In practice however, committers - who will likely
be more familiar with the commit guidelines - may decide to bring a commit up
to standard themselves.
-.. note::
-
- Before merging, but after reviewing, have Jenkins test the pull request by
- commenting "buildbot, test this please" on the PR.
- See our `Jenkins wiki page`_ for more details.
+You may want to have Jenkins test the pull request with one of the pull request
+builders that doesn't run automatically, such as Oracle or Selenium. See the
+`Jenkins wiki page`_ for instructions.
.. _Jenkins wiki page: https://code.djangoproject.com/wiki/Jenkins