# Contributing Guidelines

1. Report your full operating system details, python version and
   terminal/console program and version.
2. Ensure that your commit messages follow [these
   guidelines](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
3. Stick to the existing coding style.
4. Make sure all tests pass when run with
   [tox](https://tox.readthedocs.io/en/latest/) (missing interpreters are ok)
   and on [Travis](https://travis-ci.org/MisanthropicBit/colorise).
5. Make sure to update the documentation if necessary.

# Contributing Guidelines

1. Report your full operating system details, python version and
   terminal/console program and version.
2. Ensure that your commit messages follow [these
   guidelines](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
3. Stick to the existing coding style.
4. Make sure all tests pass when run with
   [tox](https://tox.readthedocs.io/en/latest/) (missing interpreters are ok)
   and on [Travis](https://travis-ci.org/MisanthropicBit/colorise).
5. Make sure to update the documentation if necessary and make sure that it
   builds (run `make html` in the [docs](/docs) folder).

Add docs build instructions
Add docs build instructions [ci skip]
