01 / Verification by change type
Distinguish type checks, prose, and executable examples
The validation table gives API type changes, JSDoc text changes, and JSDoc examples different commands. Documentation-only work does not need tests unless examples or code changed.
Source excerpt starting at line 17.Use the narrowest validation that covers the change: | Change type | Validation || -------------------------------- | ---------------------------------------------------------------------------------- || Code changes | `pnpm lint-fix`, targeted `pnpm test --run <test_file.ts>`, `pnpm check` || Tests-only changes | `pnpm lint-fix`, targeted `pnpm test --run <test_file.ts>`, `pnpm check` || Type-level/API type changes | Targeted `pnpm test-types <filename>`, plus `pnpm check` when source types changed || JSDoc text/category/link changes | `pnpm jsdocs --check`, `pnpm lint` || JSDoc example changes | `pnpm jsdocs --check`, `pnpm lint`, root `pnpm doctest --run <files>` || Docs-only changes | `pnpm lint-fix`; no tests unless examples or code changed |
