Contributing to docTR#
Everything you need to know to contribute efficiently to the project.
This project uses the following integrations to ensure proper codebase maintenance:
As a contributor, you will only have to ensure coverage of your code by adding appropriate unit testing of your code.
Feature requests & bug report#
Whether you encountered a problem, or you have a feature suggestion, your input has value and can be used by contributors to reference it in their developments. For this purpose, we advise you to use Github issues.
First, check whether the topic wasn’t already covered in an open / closed issue. If not, feel free to open a new one! When doing so, use issue templates whenever possible and provide enough information for other contributors to jump in.
If you are wondering how to do something with docTR, or a more general question, you should consider checking out Github discussions. See it as a Q&A forum, or the docTR-specific StackOverflow!
Developer mode installation#
Install all additional dependencies with the following command:
python -m pip install --upgrade pip pip install -e .[dev] pre-commit install
In order to run the same unit tests as the CI workflows, you can run unittests locally:
To run all quality checks together
Code style verification#
To run all style checks together
Modifying the documentation#
The current documentation is built using
sphinx thanks to our CI.
You can build the documentation locally:
Please note that files that have not been modified will not be rebuilt. If you want to force a complete rebuild, you can delete the
_build directory. Additionally, you may need to clear your web browser’s cache to see the modifications.
You can now open your local version of the documentation located at
docs/_build/index.html in your browser
Should you wish to connect somewhere else than on GitHub, feel free to join us on Slack, where you will find a