Skip to content

Latest commit

 

History

History
72 lines (48 loc) · 2.5 KB

CONTRIBUTING.md

File metadata and controls

72 lines (48 loc) · 2.5 KB

Developer's guide

This document describes how you can get started with developing Matchbox.

Dependencies

Setup

Set up environment variables by creating a .env file under project directory. See /environments/dev_local.env for sensible defaults.

This project is managed by uv, linted and formated with ruff, and tested with pytest. Docker is used for local development.

To install all dependencies for this project, run:

uv sync --all-extras

Secret scanning is done with TruffleHog.

For security, use of pre-commit is expected. Ensure your hooks are installed with pre-commit install.

Task running is done with just. To see all available commands:

just -l

Run tests

A just task is provided to run all tests.

just test

If you're running tests with some other method, such as your IDE or pytest directly, you'll need to start the local backends and mock warehouse in Docker.

docker compose up -d --wait

Standards

Code

When contributing to the main matchbox repository and its associated repos, we try to follow consistent standards. Python code should be:

  • Unit tested, and pass new and existing tests
  • Documented via docstrings, in the Google style
  • Linted and auto-formatted (just format)
  • Type hinted (within reason)
  • Using env files and dotenv for setting environment variables
  • Structured as a Python package with pyprojects.toml
  • Using dependencies managed automatically by uv
  • Integrated with justfile when relevant
  • Documented, for example, README.md files where relevant

Git

We commit as frequently as possible. We keep our commits as atomic as possible. We never push straight to main, instead we merge feature branches. Before merging to main, branches are peer reviewed.

Caution

pre-commit must be turned on. Any secrets you commit to the repo are your own responsibility.