Skip to content

Latest commit

 

History

History
72 lines (38 loc) · 2.32 KB

CONTRIBUTING.md

File metadata and controls

72 lines (38 loc) · 2.32 KB

Contributing to tawazi

Everything you need to know to contribute efficiently to the project.

Codebase structure

  • tawazi - The package codebase
  • tests - Python unit tests

Continuous Integration

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.

Feedback

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.

Questions

If you are wondering how to do something with tawazi, or a more general question, you should consider checking out GitHub discussions. See it as a Q&A forum, or the tawazi-specific StackOverflow!

Developing tawazi

Developer mode installation

Install all additional dependencies with the following command:

poetry install --with dev

and hook pre-commit

poetry run pre-commit install

Commits

  • Code: ensure to provide docstrings to your Python code. In doing so, please follow Google-style so it can ease the process of documentation later.
  • Commit message: please follow Udacity guide

Unit tests

In order to run the same unit tests as the CI workflows, you can run unittests locally:

poetry run pytest

Code quality

To run all quality checks together (static type-checking, linting, formatting, import order, and additional quality checks)

poetry run pre-commit run -a