Change references of Travis to GitHub Actions (#5536)

s/travis/github actions/g, fixes #5528

MANIFEST.in

@@ -1,8 +1,7 @@
 # stuff we need to include into the sdist is handled automatically by
 # setuptools_scm - it includes all git-committed files.
 # but we want to exclude some committed files/dirs not needed in the sdist:
-exclude .coafile .editorconfig .gitattributes .gitignore .mailmap .travis.yml Vagrantfile
-prune .travis
+exclude .coafile .editorconfig .gitattributes .gitignore .mailmap Vagrantfile
 prune .github
 include src/borg/platform/darwin.c src/borg/platform/freebsd.c src/borg/platform/linux.c src/borg/platform/posix.c
 include src/borg/platform/syncfilerange.c

README.rst

@@ -181,9 +181,9 @@ see ``docs/support.rst`` in the source distribution).
         :alt: Documentation
         :target: https://borgbackup.readthedocs.org/en/stable/
 
-.. |build| image:: https://travis-ci.com/borgbackup/borg.svg?branch=master
+.. |build| image:: https://github.com/borgbackup/borg/workflows/CI/badge.svg?branch=master
         :alt: Build Status (master)
-        :target: https://travis-ci.com/borgbackup/borg
+        :target: https://github.com/borgbackup/borg/actions
 
 .. |coverage| image:: https://codecov.io/github/borgbackup/borg/coverage.svg?branch=master
         :alt: Test Coverage

docs/development.rst

@@ -131,13 +131,13 @@ you run the tests.
 Continuous Integration
 ----------------------
 
-All pull requests go through Travis-CI_, which runs the tests on Linux
+All pull requests go through `GitHub Actions`_, which runs the tests on Linux
 and Mac OS X as well as the flake8 style checker. Windows builds run on AppVeyor_,
 while additional Unix-like platforms are tested on Golem_.
 
 .. _AppVeyor: https://ci.appveyor.com/project/borgbackup/borg/
 .. _Golem: https://golem.enkore.de/view/Borg/
-.. _Travis-CI: https://travis-ci.com/borgbackup/borg
+.. _GitHub Actions: https://github.com/borgbackup/borg/actions
 
 Output and Logging
 ------------------
@@ -322,7 +322,7 @@ Checklist:
   next milestone.
 - Check if there are any pending fixes for security issues.
 - Find and fix any low hanging fruit left on the issue tracker.
-- Check that Travis CI is happy.
+- Check that GitHub Actions CI is happy.
 - Update ``CHANGES.rst``, based on ``git log $PREVIOUS_RELEASE..``.
 - Check version number of upcoming release in ``CHANGES.rst``.
 - Render ``CHANGES.rst`` via ``make html`` and check for markup errors.