Contribution¶

Issues¶

We use GitHub issues for bug reports and feature requests.

Step-by-step guide¶

New feature¶

Make an issue with your feature description;
We shall discuss the design and its implementation details;
Once we agree that the plan looks good, go ahead and implement it.

Bugfix¶

Goto GitHub issues;
Pick an issue and comment on the task that you want to work on this feature;
If you need more context on a specific issue, please ask, and we will discuss the details.

Once you finish implementing a feature or bugfix, please send a Pull Request.

If you are not familiar with creating a Pull Request, here are some guides:

Contribution best practices¶

Install pre-commit hook:
pip install pre-commit
Break your work into small, single-purpose updates if possible. It’s much harder to merge in a large change with a lot of disjoint features.
Submit the update as a GitHub pull request against the master branch.
Make sure that you provide docstrings for all your new methods and classes
Make sure that your code passes the unit tests.
Add new unit tests for your code.

Codestyle¶

Do not forget to check the codestyle for your PR with

$ make codestyle

Documentation¶

Catalyst uses Google style for formatting docstrings. Length of line inside docstrings block must be limited to 80 characters to fit into Jupyter documentation popups.

Check that you have written working docs¶

make check-docs

The command requires Sphinx and some sphinx-specific libraries. If you don’t want to install them, you may make a catalyst-dev container

make docker-dev
docker run \\
    -v `pwd`/:/workspace/ \\
    catalyst-dev:latest \\
    bash -c "make check-docs"

To build docs add environment variable REMOVE_BUILDS=0¶

REMOVE_BUILDS=0 make check-docs

or through docker

docker run \\
    -v `pwd`/:/workspace/ \\
    catalyst-dev:latest \\
    bash -c "REMOVE_BUILDS=0 make check-docs"

The docs will be stored in builds/ folder.