xrft is meant to be a community driven package and we welcome feedback and contributions.
Did you notice a bug? Are you missing a feature? A good first starting place is to open an issue in the github issues page.
In order to contribute to xrft, please fork the repository and submit a pull request. A good step by step tutorial for this can be found in the xarray contributor guide.
The easiest way to start developing xrft pull requests, is to install one of the conda environments provided in the ci folder:
conda env create -f ci/environment-py3.8.yml
Activate the environment with:
conda activate test_env_xrft
We use black as code formatter and pull request will fail in the CI if not properly formatted.
All conda environments contain black and you can reformat code using:
pre-commit provides an automated way to reformat your code prior to each commit. Simply install pre-commit:
pip install pre-commit
and install it in the xrft root directory with:
and your code will be properly formatted before each commit.
How to release a new version of xrft (for maintainers only)¶
The process of releasing at this point is very easy.
We need only two things: A PR to update the documentation and and making a release on github.
Make sure that all the new features/bugfixes etc are appropriately documented in doc/whats-new.rst, add the date to the current release and make an empty (unreleased) entry for the next minor release as a PR.
Navigate to the ‘tags’ symbol on the repos main page, click on ‘Releases’ and on ‘Draft new release’ on the right. Add the version number and a short description and save the release.
From here the github actions take over and package things for Pypi. The conda-forge package will be triggered by the Pypi release and you will have to approve a PR in xrft-feedstock. This takes a while, usually a few hours to a day.