We appreciate your interest in contributing to Permetrics! This guide details how to contribute in a way that is efficient for everyone.
All contributors are expected to adhere to the project's Code of Conduct. Please read the document before contributing.
-
Fork the project repository and clone your fork:
git clone https://github.com/thieu1995/permetrics.git
-
Create a new branch for your changes:
git checkout -b name-of-your-branch
-
Make your changes and commit them:
git commit -m "Detailed commit message"
-
Push your changes to your fork:
git push origin name-of-your-branch
-
Create a pull request from your branch to the Permetrics main branch.
Here are some ways to contribute:
- Improve documentation
- Fix bugs or add new features
- Write tutorials or blog posts
- Review code submissions
- Test the application and report issues
However, before contributing, make sure that the unit tests pass and that new functionality is covered by unit tests.
The unit tests can be run using pytest
. Change working directory to permetrics and then use:
# Test features
python -m pytest tests/test_features
# Test comparisons
python -m pytest tests/test_comparisons
Or you can test all files by:
python -m pytest
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
main
. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Issue that pull request!
We use GitHub issues to track public bugs and requests. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue.
Don't hesitate to contact us if you have any questions. Contact @thieu1995 or ask your question on issues.
Thank you for your contributions!