First off, thanks for taking the time to contribute! 🎉
Knexa is an open-source project, and we love receiving contributions from our community — you! There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests, or writing code which can be incorporated into Knexa itself.
This project and everyone participating in it is governed by our Code of Conduct. By participating, you are expected to uphold this code.
This section guides you through submitting a bug report for Knexa. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
- Use a clear and descriptive title for the issue to identify the problem.
- Describe the exact steps which reproduce the problem in as much detail as possible.
- Provide specific examples to demonstrate the steps.
The process is described here:
- Fork the repo on GitHub.
- Clone the project to your own machine.
- Create a branch for your feature or fix (
git checkout -b feature/amazing-feature). - Commit changes to your own branch.
- Push your work back to your fork.
- Submit a Pull Request so that we can review your changes.
NOTE: Be sure to merge the latest from "upstream" before making a pull request!
- Install Python 3.9 or higher.
- Install
virtualenv:pip install virtualenv - Create a virtual environment:
virtualenv venv - Activate the virtual environment:
source venv/bin/activate - Install dependencies:
pip install -r requirements.txt
- Follow PEP 8.
- Use type hints (
typingmodule) wherever possible. - Add docstrings to all modules, classes, and functions.
- Write unit tests for new features.
Thank you for contributing!