preflight

Preflight checks validate code changes by sequentially running formatting, GN checks, presubmit, build, and test steps to ensure your branch is ready for review. The automated workflow fails fast on errors to catch issues early before submission.

To make code review-ready in Brave-derived projects, run automated preflight checks that enforce formatting, GN configuration, presubmit readiness, build success, and test targets. This prevents bad changes from being submitted and reduces review back-and-forth.

The preflight workflow selectively runs relevant tests based on your changes, but you can request all tests when needed. It enforces format, gn_check, presubmit, and build steps first, then runs tests to validate the complete change.

Yes, preflight checks run formatting and GN checks together as part of a sequential validation workflow. The process applies format, gn_check, presubmit, and build steps in order, exiting early if any step fails.

Preflight validation fails fast on errors during the build step when your code changes cannot compile successfully. The sequential checks enforce build success before running tests, ensuring bad changes are caught early and prevented from submission.

Run preflight checks on your current branch before submitting code for review. The automated validation ensures formatting, GN configuration, presubmit readiness, build success, and test passes, accelerating reviews and preventing bad changes from being submitted.