Contribution Guide

Contributions are highly welcomed and appreciated. Every little help counts, so do not hesitate! You can make a high impact on pyseaflux just by using it and reporting issues.

The following sections cover some general guidelines regarding development in pyseaflux for maintainers and contributors.

Nothing here is set in stone and can’t be changed. Feel free to suggest improvements or changes in the workflow.

Feature requests and feedback

We are eager to hear about your requests for new features and any suggestions about the API, infrastructure, and so on. Feel free to submit these as issues with the label “feature request.”

Please make sure to explain in detail how the feature should work and keep the scope as narrow as possible. This will make it easier to implement in small PRs.

Report bugs

Report bugs for seaflux in the issue tracker with the label “bug”.

If you can write a demonstration test that currently fails but should pass that is a very useful commit to make as well, even if you cannot fix the bug itself.

Fix bugs

Look through the GitHub issues for bugs.

Talk to developers to find out how you can fix specific bugs.

Preparing Pull Requests

  1. Fork the seaflux GitHub repository. It’s fine to use pyseaflux as your fork repository name because it will live under your username.

  2. Clone your fork locally using git, connect your repository to the upstream (main project), and create a branch:

    $ git clone
    $ cd SeaFlux
    $ git remote add upstream
    # now, to fix a bug or add feature create your own branch off "master":
    $ git checkout -b your-bugfix-feature-branch-name master

    If you need some help with Git, follow this quick start guide:

  3. Set up a [conda](environment) with all necessary dependencies:

    $ conda env create -f ci/environment-py3.8.yml
  4. Activate your environment:

    $ conda activate test_env_pyseaflux
  5. Install the pySeaFlux package:

    $ pip install -e . --no-deps
  6. Before you modify anything, ensure that the setup works by executing all tests:

    $ pytest

    You want to see an output indicating no failures, like this:

    $ ========================== n passed, j warnings in 17.07s ===========================
  7. Install pre-commit and its hook on the seaflux repo:

    $ pip install --user pre-commit
    $ pre-commit install

    Afterwards pre-commit will run whenever you commit. If some errors are reported by pre-commit you should format the code by running:

    $ pre-commit run --all-files

    and then try to commit again. is a framework for managing and maintaining multi-language pre-commit hooks to ensure code-style and code formatting is consistent.

    You can now edit your local working copy and run/add tests as necessary. Please follow PEP-8 for naming. When committing, pre-commit will modify the files as needed, or will generally be quite clear about what you need to do to pass the commit test.

  8. Break your edits up into reasonably sized commits:

    $ git commit -a -m "<commit message>"
    $ git push -u

    Committing will run the pre-commit hooks (isort, black and flake8). Pushing will run the pre-push hooks (pytest and coverage)

    We highly recommend using test driven development, but our coverage requirement is low at the moment due to lack of tests. If you are able to write tests, please stick to xarray’s testing recommendations.

  9. Add yourself to the

    Project Contributors list via ./docs/

  10. Finally, submit a pull request through the GitHub website using this data:

    head-fork: YOUR_GITHUB_USERNAME/pyseaflux
    compare: your-branch-name
    base-fork: lukegre/pySeaFlux
    base: master

    The merged pull request will undergo the same testing that your local branch had to pass when pushing.