- You MUST NOT manually edit
CHANGELOG.mdoutside the release workflow; it is generated.
- PREFER to use
pixi runto execute tasks instead of running executables coming from your system.
- PREFER inline snapshots over substring assertions when testing rendered output.
- New tests MUST follow local test conventions. Check existing coverage before adding tests.
- PREFER integration tests for user-visible behavior; use unit tests for isolated logic.
- PREFER running specific tests during development; run relevant broader checks before finishing.
- You MUST NOT work around limitations or bugs in rattler or rattler-build. Fix them upstream instead.
pixi run typosMUST pass. Suppress deliberate misspellings with# spellchecker:off/# spellchecker:onor their//equivalents instead of adding them toextend-words.- You MUST NOT bypass pre-commit hooks with
--no-verify.
- Use enums with variant data to represent mutually exclusive states instead of contradictory flags or dependent
Optionfields.
- Pull requests MUST follow CONTRIBUTING.md and the pull request template, including the human-written description requirement.
- Authored diagnostic messages MUST start with a lowercase letter and end without a trailing dot. This does not apply to quoted upstream errors.