running-ci-preflight

Run hogli ci:preflight --fix to format, lint, and auto-fix safe issues scoped to your changed files. Resolve every fail result and act on advisories, then re-run until clean before pushing.

It scopes checks to files your branch touched, covering formatting, lint, lockfile integrity, OpenAPI drift, migration conflicts, and branch staleness. Each check maps to a CI failure class that has taken master down.

The hook runs ci:preflight --strict, which exits non-zero on any failed check such as a real lint error, broken lockfile, or migration conflict. Fix what it reports rather than bypassing with --no-verify.

No, type-check is advisory only because only a repo-wide mypy run matches CI behavior and costs minutes cold. Preflight names the command so you can judge whether your change is type-risky and run it yourself.

Skipped checks mean a capability is absent: needs stack wants a running dev stack via hogli start, needs node wants pnpm install, and needs python-env wants uv sync. Satisfy what you can locally or let CI cover the rest.

Setting HOGLI_PREFLIGHT_DISABLED=1 makes the command and hook a no-op with exit 0. It is intended as a rollout or emergency lever and should be respected, not unset to force a run.