The main developer documentation lives in the contributing-docs directory. The following points summarise
how to set up the environment, run checks, build docs and follow the PR workflow.
07_local_virtualenv.rstexplains how to prepare a local Python environment usinguv. The tool creates and syncs a.venvand installs dependencies with commands such asuv venvanduv sync.06_development_environments.rstcompares the local virtualenv with the Docker based Breeze environment. Breeze replicates CI and includes services like databases for integration tests.
- Installation and usage of
prekare described in03a_contributors_quick_start_beginners.rst. Install withuv tool install prekand run checks viaprek --all-files. 08_static_code_checks.rstprovides more details on the available hooks and prerequisites. Enable the hooks withprek installso they run automatically on each commit.
03a_contributors_quick_start_beginners.rstshows running tests inside Breeze. Usepytestinside the container for individual files or invokebreeze testingcommands to run full suites, e.g.breeze --backend postgres --python 3.10 testing tests --test-type All.
- Documentation can be built locally using
uv run --group docs build-docsas described in11_documentation_building.rst. Within Breeze the equivalent command isbreeze build-docs.
- Follow the PR guidance in
05_pull_requests.rst. Always add tests, keep your branch rebased instead of merged, and adhere to the commit message recommendations from cbea.ms/git-commit.
For advanced topics such as packaging providers and API versioning see 12_provider_distributions.rst and 19_execution_api_versioning.rst.