Skip to content

contributing.rst

Latest commit

 

History

History
73 lines (45 loc) · 1.83 KB

contributing.rst

File metadata and controls

73 lines (45 loc) · 1.83 KB

Contributing

This page provides a guide for developers wishing to contribute to Sphinx-CodeLinks.

Bugs, Features and PRs

For bug reports and well-described technical feature requests, please use our issue tracker: https://github.com/useblocks/sphinx-codelinks/issues

If you have already created a PR, you can send it in. Our CI workflow will check (tests and code styles) and a maintainer will perform a review before we can merge it. Your PR should conform with the following rules:

  • A meaningful description or link, which describes the change
  • The changed code (for sure :) )
  • Test cases for the change (important!)
  • Updated documentation, if behavior gets changed or new options/directives are introduced.
  • Update of docs/changelog.rst.

Install Dependencies

CodeLinks uses tox (with tox-uv) to manage development tasks.

Install tox with pip or uv:

pip install tox tox-uv
uv tool install tox --with tox-uv

Formatting, Linting and Typing

To run the formatting and linting, pre-commit is used:

pre-commit install # to auto-run on every commit
pre-commit run --all-files # to run manually

The CI also checks typing. Use the following command locally to see if your code is well-typed:

tox -e mypy

Build docs

To build the documentation stored in docs, run:

tox -e docs-clean

Test Cases

To run test cases locally:

tox -e py312-sphinx8

Note some tests use syrupy to perform snapshot testing. These snapshots can be updated by running:

pytest tests/ --snapshot-update