Replace Travis CI by GitHub Actions in docs.

QuLogic · QuLogic · commit 827d86bbcf7f · 2021-02-11T19:26:28.000-05:00
diff --git a/README.rst b/README.rst
@@ -2,10 +2,10 @@
 
 |DiscourseBadge|_ |Gitter|_ |GitHubIssues|_ |GitTutorial|_
 
-|Travis|_ |AzurePipelines|_ |AppVeyor|_ |Codecov|_ |LGTM|_
+|GitHubActions|_ |AzurePipelines|_ |AppVeyor|_ |Codecov|_ |LGTM|_
 
-.. |Travis| image:: https://travis-ci.com/matplotlib/matplotlib.svg?branch=master
-.. _Travis: https://travis-ci.com/matplotlib/matplotlib
+.. |GitHubActions| image:: https://github.com/matplotlib/matplotlib/workflows/Tests/badge.svg
+.. _GitHubActions: https://github.com/matplotlib/matplotlib/actions?query=workflow%3ATests
 
 .. |AzurePipelines| image:: https://dev.azure.com/matplotlib/matplotlib/_apis/build/status/matplotlib.matplotlib?branchName=master
 .. _AzurePipelines: https://dev.azure.com/matplotlib/matplotlib/_build/latest?definitionId=1&branchName=master
diff --git a/doc/devel/coding_guide.rst b/doc/devel/coding_guide.rst
@@ -192,15 +192,15 @@ Automated tests
 Whenever a pull request is created or updated, various automated test tools
 will run on all supported platforms and versions of Python.
 
-* Make sure the Linting, Travis, AppVeyor, CircleCI, and Azure pipelines are
-  passing before merging (All checks are listed at the bottom of the GitHub
-  page of your pull request). Here are some tips for finding the cause of the
-  test failure:
+* Make sure the Linting, GitHub Actions, AppVeyor, CircleCI, and Azure
+  pipelines are passing before merging (All checks are listed at the bottom of
+  the GitHub page of your pull request). Here are some tips for finding the
+  cause of the test failure:
 
   - If *Linting* fails, you have a code style issue, which will be listed
     as annotations on the pull request's diff.
-  - If a Travis or AppVeyor run fails, search the log for ``FAILURES``. The
-    subsequent section will contain information on the failed tests.
+  - If a GitHub Actions or AppVeyor run fails, search the log for ``FAILURES``.
+    The subsequent section will contain information on the failed tests.
   - If CircleCI fails, likely you have some reStructuredText style issue in
     the docs. Search the CircleCI log for ``WARNING``.
   - If Azure pipelines fail with an image comparison error, you can find the
diff --git a/doc/devel/release_guide.rst b/doc/devel/release_guide.rst
@@ -23,9 +23,9 @@ Release Guide
 Testing
 =======
 
-We use `Travis CI <https://travis-ci.org/matplotlib/matplotlib>`__ for
-continuous integration.  When preparing for a release, the final
-tagged commit should be tested locally before it is uploaded::
+We use `GitHub Actions <https://github.com/matplotlib/matplotlib/actions>`__
+for continuous integration.  When preparing for a release, the final tagged
+commit should be tested locally before it is uploaded::
 
    pytest -n 8 .
 
@@ -251,12 +251,12 @@ We distribute macOS, Windows, and many Linux wheels as well as a source tarball
 via PyPI.  Most builders should trigger automatically once the tag is pushed to
 GitHub:
 
-* Mac and manylinux wheels are built on Travis CI.  Builds are triggered by the
-  GitHub Action defined in :file:`.github/workflows/wheels.yml`, and wheels
-  will be available at the site defined in the `matplotlib-wheels repo
-  <https://github.com/MacPython/matplotlib-wheels>`__.
-* Windows wheels are built by Christoph Gohlke automatically and will be
-  `available at his site
+* Windows, macOS and manylinux wheels are built on GitHub Actions.  Builds are
+  triggered by the GitHub Action defined in
+  :file:`.github/workflows/cibuildwheel.yml`, and wheels will be available as
+  artifacts of the build.
+* Alternative Windows wheels are built by Christoph Gohlke automatically and
+  will be `available at his site
   <https://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>`__ once built.
 * The auto-tick bot should open a pull request into the `conda-forge feedstock
   <https://github.com/conda-forge/matplotlib-feedstock>`__.  Review and merge
diff --git a/doc/devel/testing.rst b/doc/devel/testing.rst
@@ -147,34 +147,29 @@ We try to keep the tests categorized by the primary module they are
 testing.  For example, the tests related to the ``mathtext.py`` module
 are in ``test_mathtext.py``.
 
-Using Travis CI
----------------
-
-`Travis CI <https://travis-ci.com/>`_ is a hosted CI system "in the
-cloud".
-
-Travis is configured to receive notifications of new commits to GitHub
-repos (via GitHub "service hooks") and to run builds or tests when it
-sees these new commits. It looks for a YAML file called
-``.travis.yml`` in the root of the repository to see how to test the
-project.
-
-Travis CI is already enabled for the `main Matplotlib GitHub
-repository <https://github.com/matplotlib/matplotlib/>`_ -- for
-example, see `its Travis page
-<https://travis-ci.com/matplotlib/matplotlib>`_.
-
-If you want to enable Travis CI for your personal Matplotlib GitHub
-repo, simply enable the repo to use Travis CI in either the Travis CI
-UI or the GitHub UI (Admin | Service Hooks). For details, see `the
-Travis CI Getting Started page
-<https://docs.travis-ci.com/user/getting-started/>`_.  This
-generally isn't necessary, since any pull request submitted against
-the main Matplotlib repository will be tested.
-
-Once this is configured, you can see the Travis CI results at
-https://travis-ci.org/your_GitHub_user_name/matplotlib -- here's `an
-example <https://travis-ci.org/msabramo/matplotlib>`_.
+Using GitHub Actions for CI
+---------------------------
+
+`GitHub Actions <https://docs.github.com/en/actions>`_ is a hosted CI system
+"in the cloud".
+
+GitHub Actions is configured to receive notifications of new commits to GitHub
+repos and to run builds or tests when it sees these new commits. It looks for a
+YAML files in ``.github/workflows`` to see how to test the project.
+
+GitHub Actions is already enabled for the `main Matplotlib GitHub repository
+<https://github.com/matplotlib/matplotlib/>`_ -- for example, see `the Tests
+workflows
+<https://github.com/matplotlib/matplotlib/actions?query=workflow%3ATests>`_.
+
+GitHub Actions should be automatically enabled for your personal Matplotlib
+fork once the YAML workflow files are in it. It generally isn't necessary to
+look at these workflows, since any pull request submitted against the main
+Matplotlib repository will be tested.
+
+You can see the GitHub Actions results at
+https://github.com/your_GitHub_user_name/matplotlib/actions -- here's `an
+example <https://github.com/QuLogic/matplotlib/actions>`_.
 
 
 Using tox
