Thanks for helping!
We welcome all kinds of contributions:
- Bug fixes
- Documentation improvements
- New features
- Refactoring & tidying
If you have a specific contribution in mind, be sure to check the issues and pull requests in progress - someone could already be working on something similar and you can help out.
Several tools are used to ensure a coherent coding style. You need to make sure that your code satisfy those requirements or the automated tests will fail.
On Linux or MacOS, you can fix and check your code style by running
the command style.sh --fix
On Windows, you can fix and check your code by running
the command style.cmd --fix
To only verify the code without making changes, run the above script without --fix
To install the correct development dependencies of the linting tools described above, run:
python -m pip install -r requirements.dev.txt
To setup a pre-commit hook to verify your code at each commit:
On linux, run:
ln -s ../../style.sh ./.git/hooks/pre-commit
On windows, put this in ./.git/hooks/pre-commit :
#!/bin/sh
sh style.sh
- Make a fork of the main branch on github
- Clone your forked repo on your computer
- Create a feature branch
git checkout -b feature_my_awesome_feature
- Modify the code
- Verify that the Coding guidelines are respected
- Make a commit and push it to your fork
- From github, create the pull request. Automated tests from GitHub actions will then automatically check the style
- If other modifications are needed, you are free to create more commits and push them on your branch. They'll get added to the PR automatically.
Once the Pull Request is accepted and merged, you can safely delete the branch (and the forked repo if no more development is needed).