Contributing to pyjelly
Hello! If you want to contribute to Jelly and help us make it go fast (in Python), please follow the rules described below.
Quick start
-
Clone the project with
git clone https://github.com/Jelly-RDF/pyjelly.git. -
If it's not already installed on your machine, install uv. uv is the project manager of choice for pyjelly.
- Make sure you have the correct version of uv installed. You can find it in
pyproject.tomlunder[tool.uv]asrequired-version. If you have installed uv through the dedicated standalone installer, you can change the version throughuv self update:
- Make sure you have the correct version of uv installed. You can find it in
-
Install the project to a virtual environment (typically
.venvin the project directory) withuv sync.- If you use an IDE, make sure that it employs the Python interpreter from that environment.
-
Activate the environment or use
uv runto run commands and code.
Submit Feedback
The best way to send feedback is to file an issue at https://github.com/Jelly-RDF/pyjelly/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome. ;)
Contributions
- Every major pull request should be connected to an issue. If you see a problem, first create an issue.
- For minor issues (typos, small fixes) make sure you describe your problem well in the PR.
- Every new branch should follow the naming convention of
GH-<issue-number>-<description>.- For minor issues name the branch
GH-minor-<description>.
- For minor issues name the branch
- When opening a pull request:
- Use a descriptive title.
- Reference the related issue in the description.
- Please make sure your code passes all the checks:
- Tests (
pytest) - Type safety (
mypy) - Formatting and linting (
ruffor viapre-commit) This helps us follow best practices and keep the codebase in shape.