Drop Travis in favor of Github workflow (#1488)

* Drop Travis CI

* Update DEPLOY.md about new workflow of uploading new version to PyPI

* Upload coverage data to Codecov

Co-Authored-By: Steve Kowalik <steven@wedontsleep.org>

.github/workflows/check.yml

@@ -14,9 +14,14 @@ jobs:
         uses: actions/setup-python@v1
         with:
           python-version: "${{ matrix.python-version }}"
-      - name: "Install dependencies"
+      - name: Install tox
         run: |
           python -m pip install --upgrade pip
           pip install tox tox-gh-actions
       - name: Test with tox
         run: tox
+      - name: Upload coverage to Codecov
+        if: matrix.python-version == 3.6
+        uses: codecov/codecov-action@v1
+        with:
+          file: ./.coverage

DEPLOY.md

@@ -1,6 +1,6 @@
 ## Upload a new version to PyPI
 
-Travis-ci will push tagged commits to PyPI. Here are the steps:
+Github workflow (`.github/workflows/python-publish.yml`) will push tagged commits to PyPI. Here are the steps:
 
 1. Run `manage.py` 
 
@@ -9,10 +9,11 @@ Travis-ci will push tagged commits to PyPI. Here are the steps:
 Next version number? (previous: 'XXX')
 ```
 
-2. Give the new version number based on previous version (see semantic release)
+2. Give the new version number based on previous version (Use semantic versioning)
 
-3. Now the push will be on hold until you press Enter. Manually inpect the changelog (`doc/changes.rst`) to make changes if necessary. Once you are sure, go back and press Enter. 
+3. Create a new Github [release](https://github.com/PyGithub/PyGithub/releases) from the tag that has just been committed, with the same release note from `doc/changes.rst`. This step is the hook that will trigger the workflow. (also needed for some web spiders for changelog parsing)
+
+4. Now the push will be on hold until you press Enter. Manually inspect the changelog (`doc/changes.rst`) to make changes if necessary. Once you are sure, go back and press Enter. 
 
-4. Once the travis job (Python 3.5) is done, the new version should be uploaded to PyPI.
+5. Once the `python-publish` workflow completes, a new version will appear on [PyPI](https://pypi.org/project/PyGithub/#history) shortly.
 
-5. Update the Github [release](https://github.com/PyGithub/PyGithub/releases) page with the same release note from `doc/changes.rst`. (needed for some web spiders for changelog parsing)

doc/examples/Repository.rst

@@ -62,7 +62,6 @@ Get all of the contents of the root directory of the repository
     ...
     ContentFile(path=".github")
     ContentFile(path=".gitignore")
-    ContentFile(path=".travis.yml")
     ContentFile(path="CONTRIBUTING.md")
     ContentFile(path="COPYING")
     ContentFile(path="COPYING.LESSER")
@@ -91,7 +90,6 @@ Get all of the contents of the repository recursively
     ...         print(file_content)
     ...
     ContentFile(path=".gitignore")
-    ContentFile(path=".travis.yml")
     ContentFile(path="CONTRIBUTING.md")
     ...
     ContentFile(path="github/tests/ReplayData/Team.testRepoPermission.txt")