From 4dc30dabab16602a0e6cf9348ecd385aab13a775 Mon Sep 17 00:00:00 2001 From: Justin Mayer Date: Tue, 12 Nov 2019 14:13:43 -0800 Subject: [PATCH] Update `hub pull-request` docs in CONTRIBUTING --- CONTRIBUTING.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index ac120128..5c1086a1 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -120,12 +120,13 @@ Using Git and GitHub GitHub's web UI to submit the pull request. This isn't an absolute requirement, but makes the maintainers' lives much easier! Specifically: `install hub `_ and then run - `hub pull-request `_ to - turn your GitHub issue into a pull request containing your code. -* After you have issued a pull request, Travis will run the test suite for all - supported Python versions and check for PEP8 compliance. If any of these - checks fail, you should fix them. (If tests fail on Travis but seem to pass - locally, ensure that local test runs aren't skipping any tests.) + `hub pull-request -i [ISSUE] `_ + to turn your GitHub issue into a pull request containing your code. +* After you have issued a pull request, the continuous integration (CI) system + will run the test suite for all supported Python versions and check for PEP8 + compliance. If any of these checks fail, you should fix them. (If tests fail + on the CI system but seem to pass locally, ensure that local test runs aren't + skipping any tests.) Contribution quality standards ------------------------------