CLN: remove references of Travis (#41928)

Author: fangchenli

README.md

@@ -10,7 +10,6 @@
 [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.3509134.svg)](https://doi.org/10.5281/zenodo.3509134)
 [![Package Status](https://img.shields.io/pypi/status/pandas.svg)](https://pypi.org/project/pandas/)
 [![License](https://img.shields.io/pypi/l/pandas.svg)](https://github.com/pandas-dev/pandas/blob/master/LICENSE)
-[![Travis Build Status](https://travis-ci.org/pandas-dev/pandas.svg?branch=master)](https://travis-ci.org/pandas-dev/pandas)
 [![Azure Build Status](https://dev.azure.com/pandas-dev/pandas/_apis/build/status/pandas-dev.pandas?branch=master)](https://dev.azure.com/pandas-dev/pandas/_build/latest?definitionId=1&branch=master)
 [![Coverage](https://codecov.io/github/pandas-dev/pandas/coverage.svg?branch=master)](https://codecov.io/gh/pandas-dev/pandas)
 [![Downloads](https://anaconda.org/conda-forge/pandas/badges/downloads.svg)](https://pandas.pydata.org)

doc/source/_static/ci.png

@@ -407,12 +407,12 @@ pandas uses `mypy <http://mypy-lang.org>`_ to statically analyze the code base a
 Testing with continuous integration
 -----------------------------------
 
-The pandas test suite will run automatically on `Travis-CI <https://travis-ci.org/>`__ and
+The pandas test suite will run automatically on `GitHub Actions <https://github.com/features/actions/>`__ and
 `Azure Pipelines <https://azure.microsoft.com/en-us/services/devops/pipelines/>`__
 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 <http://about.travis-ci.org/docs/user/getting-started/>`__ and
+for `GitHub Actions <https://docs.github.com/en/actions/>`__ and
 `Azure Pipelines <https://docs.microsoft.com/en-us/azure/devops/pipelines/>`__.
 
 A pull-request will be considered for merging when you have an all 'green' build. If any tests are failing,
@@ -421,12 +421,6 @@ This is an example of a green build.
 
 .. image:: ../_static/ci.png
 
-.. note::
-
-   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 <https://docs.travis-ci.com/user/customizing-the-build/#Building-only-the-latest-commit>`__.
-
 .. _contributing.tdd:
 
 

doc/source/development/contributing_codebase.rst

@@ -35,22 +35,11 @@ def _skip_if_no_private_key_path():
         pytest.skip("Cannot run integration tests without a private key json file path")
 
 
-def _in_travis_environment():
-    return "TRAVIS_BUILD_DIR" in os.environ and "GBQ_PROJECT_ID" in os.environ
-
-
 def _get_project_id():
-    if _in_travis_environment():
-        return os.environ.get("GBQ_PROJECT_ID")
     return PROJECT_ID or os.environ.get("GBQ_PROJECT_ID")
 
 
 def _get_private_key_path():
-    if _in_travis_environment():
-        return os.path.join(
-            *[os.environ.get("TRAVIS_BUILD_DIR"), "ci", "travis_gbq.json"]
-        )
-
     private_key_path = PRIVATE_KEY_JSON_PATH
     if not private_key_path:
         private_key_path = os.environ.get("GBQ_GOOGLE_APPLICATION_CREDENTIALS")