presubmit

Automate code quality checks by running presubmit validation to execute tests, linting, type checking, and static analysis before merge. This catches issues early, reduces regressions, and enforces policy conformance across your repository in a single deterministic step.

Presubmit runs linting, unit tests, type checks, and static analysis together. These comprehensive checks validate code correctness, quality, and policy compliance, surfacing problems before code reaches the main branch.

Yes. Presubmit checks integrate into CI workflows to enforce code quality gates before merge. Run the presubmit script from your repository root, capture output, and use results to block or approve merges based on conformance.

Review presubmit output to identify failures in linting, tests, or static analysis. Fix the underlying issues—code errors, style violations, or type mismatches—then rerun presubmit to confirm all checks pass before proceeding.

For large refactors and feature branches, run the presubmit script from your repository root to validate all changes at once. This deterministic approach ensures consistent results and surfaces correctness issues across the entire refactored codebase.

Presubmit automates technical validation—linting, testing, and policy checks—but does not replace code review. After checks pass, human review ensures design quality and business logic correctness before merge.