PEP 101: temporarily disable CI status checks too.

pep-0101.txt

@@ -651,10 +651,13 @@ Now it's time to do some cleaning up.  These steps are very important!
   this branch" box and add yourself.  Also, uncheck the "Include
   administrators" box and save changes.
 
-  (Branches which are in "security fixes only" mode are already
-  restricted, and you should be a member of the list of people
-  permitted to push to the branch.  So for "security fixes only"
-  branches, this step is a no-op.)
+  (This step isn't necessary for branches already in "security fixes mode".
+  However, the next step is!)
+
+- While you're editing the settings for your branch, you'll also need to
+  uncheck "Require status checks to pass before merging".  This temporarily
+  disables requiring CI status checks (Travis, AppVeyor, etc) be run and
+  passed before a revision may be pushed.
 
 - Merge your release clone into the main development repo::
 
@@ -690,11 +693,17 @@ Now it's time to do some cleaning up.  These steps are very important!
   undo those temporary changes now.
   https://github.com/python/cpython/settings/branches/
 
-  Uncheck the "Retrict who can push to this branch".  Check the "Include
-  administrators" box and save changes.
+  A reminder of changes you may have made:
 
-  (Again, this doesn't apply to "security fixes only" branches.  This step,
-  too, is a no-op for those branches.)
+  - Uncheck the "Retrict who can push to this branch".  (Only necessary
+    if the branch is not in "security-fixes-only mode".)
+
+  - Check the "Include administrators" box.  (Only necessary
+    if the branch is not in "security-fixes-only mode".)
+
+  - Check the "Require status checks to pass before merging" box.  (Always needed.)
+
+  Save your changes.
 
 - You can delete the remote release clone, or simply reuse it for the next
   release.