There has been a recent leak at Travis CI where private secrets could
exposed in PRs from forks
(https://twitter.com/peter_szilagyi/status/1437646118700175360?s=20).
Remove Travis configuration script to avoid triggering a build here and
revoke Travis access to our organization to be safe.
Reminders:
[ ] Run make format and make check to make sure the code follows the style guide.
[ ] Add tests for new features or tests that would have caught the bug that you're fixing.
[ ] Add new public functions/methods/classes to doc/api/index.rst and the base __init__.py file for the package.
[ ] Write detailed docstrings for all functions/classes/methods. It often helps to design better code if you write the docstrings first.
[ ] If adding new functionality, add an example to the docstring, gallery, and/or tutorials.
[ ] Add your full name, affiliation, and ORCID (optional) to the AUTHORS.md file (if you haven't already) in case you'd like to be listed as an author on the Zenodo archive of the next release.
There has been a recent leak at Travis CI where private secrets could exposed in PRs from forks (https://twitter.com/peter_szilagyi/status/1437646118700175360?s=20). Remove Travis configuration script to avoid triggering a build here and revoke Travis access to our organization to be safe.
Reminders:
make formatandmake checkto make sure the code follows the style guide.doc/api/index.rstand the base__init__.pyfile for the package.AUTHORS.mdfile (if you haven't already) in case you'd like to be listed as an author on the Zenodo archive of the next release.