Remove Travis cruft.

CHANGES.rst

@@ -2,6 +2,12 @@
 Changes
 =======
 
+Unreleased
+----------
+
+- Move tests to GitHub Actions
+  [jezdez]
+
 
 5.9.0 (2020-11-05)
 ------------------

README.rst

@@ -18,9 +18,9 @@ django-axes
    :target: https://django-axes.readthedocs.io/
    :alt: Documentation
 
-.. image:: https://secure.travis-ci.org/jazzband/django-axes.svg?branch=master
-   :target: http://travis-ci.org/jazzband/django-axes
-   :alt: Build Status
+.. image:: https://github.com/jazzband/django-axes/workflows/Test/badge.svg
+   :target: https://github.com/jazzband/django-axes/actions
+   :alt: GitHub Actions
 
 .. image:: https://codecov.io/gh/jazzband/django-axes/branch/master/graph/badge.svg
    :target: https://codecov.io/gh/jazzband/django-axes
@@ -89,7 +89,7 @@ Merging contributions requires passing the checks configured
 with the CI. This includes running tests and linters successfully
 on the currently officially supported Python and Django versions.
 
-The test automation is run automatically by Travis CI, but you can
+The test automation is run automatically with GitHub Actions, but you can
 run it locally with the ``tox`` command before pushing commits.
 
 Please note that this is a `Jazzband <https://jazzband.co>`_ project.

docs/1_requirements.rst

@@ -7,9 +7,9 @@ Axes requires a supported Django version and runs on Python versions 3.6 and abo
 
 Refer to the project source code repository in
 `GitHub <https://github.com/jazzband/django-axes/>`_ and see the
-`Travis CI configuration <https://github.com/jazzband/django-axes/blob/master/.travis.yml>`_ and
+`Tox configuration <https://github.com/jazzband/django-axes/blob/master/tox.ini>`_ and
 `Python package definition <https://github.com/jazzband/django-axes/blob/master/setup.py>`_
 to check if your Django and Python version are supported.
 
-The `Travis CI builds <https://travis-ci.org/jazzband/django-axes>`_
+The `GitHub Actions builds <https://github.com/jazzband/django-axes/actions>`_
 test Axes compatibility with the Django master branch for future compatibility as well.

docs/9_development.rst

@@ -37,7 +37,7 @@ Before committing, you can run all the above tests against all supported Python
 
     $ tox
 
-Tox runs the same test set that is run by Travis, and your code should be good to go if it passes.
+Tox runs the same test set that is run by GitHub Actions, and your code should be good to go if it passes.
 
 If you wish to limit the testing to specific environment(s), you can parametrize the tox run::