Use GitHub Actions instead of Travis and Azure. Use nox instead of the Makefile
to manage creating environments and running the tests, docs, checks, etc. The
main advantage is that the configuration (noxfile.py) is Python and
cross-platform. Since nox creates the environments, we don't need to install
anything but nox in the conda environment. This simplifies keeping track of
dependencies both locally and on CIs. Had to use conda to build the docs
because cartopy wouldn't install with pip.
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.
Use GitHub Actions instead of Travis and Azure. Use nox instead of the Makefile to manage creating environments and running the tests, docs, checks, etc. The main advantage is that the configuration (
noxfile.py) is Python and cross-platform. Since nox creates the environments, we don't need to install anything but nox in the conda environment. This simplifies keeping track of dependencies both locally and on CIs. Had to use conda to build the docs because cartopy wouldn't install with pip.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.