Contributing
Contributing to BioContext7
BioContext7 is built for the bioinformatics community. There are many ways to contribute, from reporting bugs to submitting new tools.
Ways to Contribute
Report a Bug
Found something broken? Let us know so we can fix it. Include steps to reproduce, expected behavior, and any error messages.
Email us →
Suggest a Feature
Have an idea for a new tool, integration, or improvement? We welcome feature requests from the community.
Send a suggestion →
Submit a Tool
Know a bioinformatics tool that should be in our registry? Submit it for inclusion in the BioContext7 database.
Submit a tool →
Improve Documentation
Help us improve our documentation by reporting unclear sections, suggesting edits, or contributing guides.
Contact us →
Development Guidelines
Code Quality
We use ruff for Python linting (target Python 3.11+, 120-character lines) and ESLint + Prettier for TypeScript. All contributions must pass CI checks before merge.
Testing
Python packages use pytest; TypeScript packages use vitest. Every new feature should include tests. Mark slow or integration tests appropriately.
Commit Messages
We follow Conventional Commits. Use prefixes like feat:, fix:, or docs: for your commit messages.
Questions about contributing? Reach out to us