From ac3803f446627875fbb46836b1aa28bb1f327027 Mon Sep 17 00:00:00 2001 From: Krishna Date: Tue, 23 Oct 2018 17:18:22 +0100 Subject: [PATCH 1/2] DOC: Updated references of Appveyor to Azure pipelines --- doc/source/contributing.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/source/contributing.rst b/doc/source/contributing.rst index f898ef54e4101..76bd026c3ac4d 100644 --- a/doc/source/contributing.rst +++ b/doc/source/contributing.rst @@ -657,12 +657,12 @@ Testing With Continuous Integration ----------------------------------- The *pandas* test suite will run automatically on `Travis-CI `__, -`Appveyor `__, and `Circle CI `__ continuous integration -services, once your pull request is submitted. +`Azure Pipelines `__, + and `Circle CI `__ continuous integration services, once your pull request is submitted. However, if you wish to run the test suite on a branch prior to submitting the pull request, then the continuous integration services need to be hooked to your GitHub repository. Instructions are here for `Travis-CI `__, -`Appveyor `__ , and `CircleCI `__. +`Azure Pipelines `__ , and `CircleCI `__. A pull-request will be considered for merging when you have an all 'green' build. If any tests are failing, then you will get a red 'X', where you can click through to see the individual failed tests. @@ -672,8 +672,8 @@ This is an example of a green build. .. note:: - Each time you push to *your* fork, a *new* run of the tests will be triggered on the CI. Appveyor will auto-cancel - any non-currently-running tests for that same pull-request. You can enable the auto-cancel feature for + Each time you push to *your* fork, a *new* run of the tests will be triggered on the CI. + You can enable the auto-cancel feature, which removes any non-currently-running tests for that same pull-request, for `Travis-CI here `__ and for `CircleCI here `__. From f78c27199b4484879eace6f36591eab904380e86 Mon Sep 17 00:00:00 2001 From: Krishna Date: Tue, 23 Oct 2018 17:40:54 +0100 Subject: [PATCH 2/2] DOC: Updated references of Appveyor to Azure pipelines (formatting) --- doc/source/contributing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/contributing.rst b/doc/source/contributing.rst index 76bd026c3ac4d..67b8d287d5d1a 100644 --- a/doc/source/contributing.rst +++ b/doc/source/contributing.rst @@ -658,11 +658,11 @@ Testing With Continuous Integration The *pandas* test suite will run automatically on `Travis-CI `__, `Azure Pipelines `__, - and `Circle CI `__ continuous integration services, once your pull request is submitted. +and `Circle CI `__ continuous integration services, once your pull request is submitted. However, if you wish to run the test suite on a branch prior to submitting the pull request, then the continuous integration services need to be hooked to your GitHub repository. Instructions are here for `Travis-CI `__, -`Azure Pipelines `__ , and `CircleCI `__. +`Azure Pipelines `__, and `CircleCI `__. A pull-request will be considered for merging when you have an all 'green' build. If any tests are failing, then you will get a red 'X', where you can click through to see the individual failed tests.