Buildkite Preflight

Preflight runs CI builds against changes in the local working directory. It's intended to provide a feedback loop for evaluating local changes in CI by providing a single command to run the entire commit/push/run loop.

When to Run Preflight

• After completing the requested implementation and local tests pass, use preflight to run the whole test suite on CI
• Before a long unsupervised session ends if you've made multiple changes
• After fixing a failure from a previous preflight run
• Not for trivial changes like typos, comment-only edits, or single-line config tweaks unless the user asks
• When the user asks to verify changes work in CI

Before Running

• Prefer an explicit pipeline in {org}/{pipeline} form
• Ensure bk auth is pointed at the right Buildkite organization when the pipeline slug relies on local config
• Requires a git repository with at least one commit and push access to origin
• Requires read_builds, write_builds, and read_pipelines scopes; and read_suites for Test Engine results.
• Run preflight in a subagent