We expect contributors to keep this project professional, respectful, and technically grounded. Good participation includes:
- Treating other contributors with respect, patience, and good faith.
- Keeping technical disagreement focused on evidence, maintainability, correctness, and user impact.
- Giving actionable review feedback with enough context for the author to respond.
- Receiving review feedback as part of improving the change, not as a personal dispute.
- Preserving clear tests, documentation, package boundaries, and security hygiene.
- Being transparent about uncertainty, tradeoffs, and known limitations.
- Helping keep issues and pull requests organized with accurate titles, labels, summaries, and testing notes.
Contributions should improve or preserve the long-term health of the project. We expect contributors to:
- Keep changes focused on the stated problem.
- Prefer simple, robust, scalable designs over shortcuts.
- Reproduce bugs as close to the user experience as practical before narrowing them to focused tests.
- Add tests for changed public behavior and bug fixes.
- Keep secrets, local artifacts, generated private deployment state, and build output out of the repository.
- Respect the TypeScript monorepo's package and dependency boundaries.
- Keep documentation accurate when behavior changes.
The following conduct is not acceptable:
- Harassment, threats, personal attacks, insults, or discriminatory language.
- Dismissive review comments that do not explain the technical concern.
- Repeatedly derailing issues or pull requests away from the stated topic.
- Publishing private information without permission.
- Submitting malicious code, intentionally misleading changes, or changes that hide security risk.
- Pressuring maintainers or contributors to bypass review, tests, or documented project processes.
Maintainers may edit, hide, or remove comments, issues, pull requests, or other contributions that violate this code of conduct. Maintainers may also warn contributors, temporarily limit participation, or block participation when conduct harms the project or its contributors.
Report concerns privately through the repository maintainers or the contact paths on diffex.ai. Reports should include relevant links, screenshots, dates, and a short description of the concern when possible. Maintainers will limit disclosure to the people needed to review and address the report.