ci-compliance

Pre-push CI checks for a monorepo are automated by detecting changed files and routing subsystem-specific validation, running golangci-lint, go test -race, npm lint/build, and pytest to prevent remote push failures.

Validating commit message format before pushing is handled by enforcing project guidelines through an automated pre-push runbook, ensuring team CI/CD standards for commit hygiene are met prior to remote code transfer.

Running lint and build checks only on changed files in a monorepo is supported by detecting modified files and routing appropriate checks, executing targeted golangci-lint, npm lint/typecheck, and pytest validations.

Pre-push CI validation works with pip-audit and go test -race by routing subsystem-specific checks, executing Go race condition tests, Python pytest, and pip-audit vulnerability scanning based on detected changed files.

Failing npm lint and typecheck tests in CI after pushing web changes happen when pre-push validation is skipped, meaning format, typecheck, and build requirements were not verified against project standards before remote transfer.