Files
yvgude--lean-ctx/rust/eval/testbench/repos/qa-api/CONTRIBUTING.md
T
wehub-resource-sync 26382a7ac6
CI / Clippy (push) Failing after 15m13s
CI / Test (ubuntu-latest) (push) Failing after 16m1s
CI / Test (macos-latest) (push) Has been cancelled
CI / Test (windows-latest) (push) Has been cancelled
CI / Build (no embeddings / no ORT) (push) Has been cancelled
CI / Format (push) Has been cancelled
CI / Cookbook (Node) (push) Has been cancelled
CI / Pi Extension (Node) (push) Has been cancelled
CI / Rust SDK (lean-ctx-client) (push) Has been cancelled
CI / Embed SDK (lean-ctx-sdk) (push) Has been cancelled
CI / Python SDK (leanctx) (push) Has been cancelled
CI / Hermes Plugin (Python) (push) Has been cancelled
CI / SDK Conformance Matrix (push) Has been cancelled
CI / Coverage (push) Has been cancelled
CI / cargo-deny (push) Has been cancelled
CI / Adversarial Safety (push) Has been cancelled
CI / Benchmarks (push) Has been cancelled
CI / Output-Quality Gate (eval A/B) (push) Has been cancelled
CI / Documentation (push) Has been cancelled
CI / CI Green (push) Has been cancelled
JetBrains Plugin / Actionlint (push) Has been cancelled
CodeQL / Analyze (actions) (push) Has been cancelled
CodeQL / Analyze (javascript-typescript) (push) Has been cancelled
CodeQL / Analyze (rust) (push) Has been cancelled
JetBrains Plugin / Validation (push) Has been cancelled
JetBrains Plugin / Build (push) Has been cancelled
JetBrains Plugin / Test (push) Has been cancelled
Security Check / Security Scan (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:35:30 +08:00

891 B

Contributing

Thank you for considering a contribution. This document is generic onboarding boilerplate and deliberately contains no information about the retry policy.

Code of conduct

Be kind. Be respectful. Assume good intent. Disagreement is fine; rudeness is not.

Development setup

  1. Clone the repository.
  2. Install the toolchain.
  3. Run the test suite.
  4. Make your change on a feature branch.
  5. Open a merge request and request review.

Style

  • Keep functions small and focused.
  • Write a test for every behavioural change.
  • Document non-obvious intent, not the obvious.
  • Run the formatter and the linter before pushing.

Review process

A maintainer will review your change, request changes if needed, and merge it once the pipeline is green and at least one approval has been granted. Please be patient; reviews are done on a best-effort basis by volunteers.