land-the-plane

Local CI validation lets you run lint, typecheck, test, and build checks before merging. It discovers applicable commands from your repository and executes them in parallel to provide a clear summary of whether your code changes are ready to merge.

Yes, you can validate code changes locally without pushing. Local pre-merge validation discovers and runs applicable lint, typecheck, test, and build commands directly on your machine, ensuring your code changes meet quality gates before you submit a PR.

Yes, local pre-merge validation requires jq and a SHA-1 utility such as sha1sum or shasum. These dependencies are used by the local scripts to coordinate tasks and execute commands in parallel via an autoland-style workflow.

The best way to speed up local lint and test execution is running checks in parallel. An autoland-like workflow coordinates tasks via a sub-agent to execute commands concurrently, providing faster feedback on whether your PR is ready to merge.

Local CI discovery auto-detects applicable lint, typecheck, test, and build commands directly from your repository configuration. You can list the discovered commands using a dedicated shell script before executing them for pre-merge assurance.