Skip to content

Make a development guide #220

@settwi

Description

@settwi

We need a guide that says how to initialize a dev environment and run it properly. It could just be a markdown file on GitHub; it doesn't need to necessarily be an offical document that we put into Sphinx. It would be good to link to relevant documentation as well in case something breaks in the future.

There are several tools used to check the code:

  • tox (which manages the rest of them)
  • ruff
  • buildthedocs/sphinx
  • isort
  • codecov
  • GH actions & their configurations
  • pytest
  • pre-commit
  • ...?

It's not immediately clear what all is required. For instance

  • do we need isort if we have ruff?
  • Should we have a setup.py when we have a pyproject.toml?

Let's document how things work, decide what we need/don't need, then remove what we don't?

Metadata

Metadata

Assignees

No one assigned

    Labels

    DiscussionAn issue opened for, or undergoing discussion.DocumentationAffects the documentation.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions