Issues and Planning

We manage open tasks, planned features, and bugs in the issues section of the GitHub repository. Opening or joining an issue is the standard first step before opening a PR.

Writing an issue

If you find a bug, documentation issue, feature request, or general suggestion:

• Check whether an issue already exists.

• If yes, add context there instead of opening a duplicate.

• If no, open a new issue with a precise description.

• Use labels and milestones to indicate category and priority.

For integration/tutorial suggestions (especially scverse-related), include:

• Which package(s) should be integrated.

• The concrete user story or analysis workflow.

• What should be covered: API integration, data exchange, or full tutorial.

• Any example dataset or notebook reference.

Working on an issue

If you want to contribute but do not know where to start, browse existing issues and start with clearly scoped tasks.