pre-push-quality-checks

Pre-push quality checks prevent bad commits by running dependency installation, auto-fix, formatting, type checking, and linting on changed source files before any push or PR creation.

Enforcing code quality before a git push requires installing dependencies with bun install, then sequentially running bun run fix, bun run format, bun run type, and bun run lint to validate all changes.

Yes, you can block PR creation if checks fail. The workflow acts as a guardrail for git workflows, preventing pushes and pull requests when any type checking or linting errors remain in the changed files.

Pre-push hooks handle dependency installation by making bun install a mandatory first step, ensuring the environment is consistent before executing formatting, type checking, and linting validation.

The best way to automate formatting and linting before merging is running a standardized sequence of fix, format, type, and lint commands that enforce end-to-end quality compliance on all changed source files.

Your git push fails when type checking finds errors because the quality workflow includes guardrails that block code submission, ensuring no low-quality changes enter the main branches until all errors are resolved.