code-quality-standards

GitHub Actions workflows enforce code quality by running linting, type-checking, testing, and coverage gates on every pull request. Define required checks in your CI pipeline to catch issues before merge, ensuring consistent standards across your codebase.

Vitest coverage focuses on testing at module boundaries rather than hitting arbitrary percentages. Define coverage thresholds that reflect actual risk, measure what matters for reliability, and use patch coverage to enforce quality on changed code only.

Git hooks run pre-commit and pre-push checks automatically, catching linting, formatting, type, and test failures instantly without manual intervention. This immediate feedback prevents low-quality code from entering version control.

Yes. Git hooks, GitHub Actions, and Vitest coverage configuration apply consistently across projects by standardizing your quality gates—linting, type-checking, testing, and build—ensuring uniform baseline standards.

Failed quality gates block merges until issues resolve. GitHub Actions surfaces lint errors, type mismatches, test failures, and coverage gaps in pull request checks, forcing fixes before code reaches the main branch.

Pre-commit hooks typically run fast checks (linting, formatting, type-checking), while pre-push hooks or CI run the full test suite. This staged approach catches obvious problems early and reserves heavy testing for the CI pipeline.