Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
63 lines (49 loc) · 2.67 KB

CONTRIBUTING.md

File metadata and controls

63 lines (49 loc) · 2.67 KB
Raw

Contributing to OpenMed

Thanks for helping improve OpenMed — bug reports, features, docs, and translations are all welcome. By participating you agree to our Code of Conduct.

Important

Security and privacy come first. OpenMed de-identifies PHI. Never open a public issue for a vulnerability, and never include real patient data in an issue, pull request, test, or fixture — see SECURITY.md. Any test data committed to the repository must be synthetic.

This page is a quick start. The full tooling, documentation, and release guide lives in docs/contributing.md.

Development setup

uv pip install -e ".[dev]"      # editable install with test + lint deps
# stack extras as needed, e.g. ".[dev,hf]" for Hugging Face model work
pre-commit install              # auto-format staged files on commit

The pre-commit hooks also run the Gitleaks secret scanner on staged changes. See Secret Scanning for local use, CI behavior, and baseline maintenance.

Run the checks before opening a PR

.venv/bin/python -m pytest tests/ -q     # run the test suite
make format                              # apply canonical Ruff formatting
make lint                                # lint
make type-check                          # scoped public-module type check
make format-check                        # CI-parity format check

Ruff is the single source of truth for Python lint, import ordering, and formatting; the pinned mypy gate checks the annotated public-module scope. CI runs both gates. Do not run Black, isort, or flake8. For Swift changes under swift/OpenMedKit, run make format-swift and make lint-swift.

Pull requests

  • Keep each PR focused on a single feature or fix; avoid unrelated formatting churn.
  • Write clear, imperative commit messages (the project uses concise prefixes such as fix:, feat:, and docs:).
  • Reference the issue you are closing and complete the pull request template.
  • Update CHANGELOG.md and the docs when behavior changes.
  • For privacy-sensitive paths, add tests for direct-identifier recall, critical leakage, and span integrity (see docs/contributing.md).

Reporting issues

  • Bugs and features: use the issue templates.
  • Security vulnerabilities (including redaction bypass or PHI/PII leakage): report privately per SECURITY.md — never as a public issue.

For the complete contributor and release workflow, see docs/contributing.md.