CI checks

CI should run the same deterministic checks developers trust before merge: install, lint, typecheck, unit and integration tests, build, and domain-specific validation such as content or schema checks. Flaky CI erodes confidence faster than missing tests. Cache dependencies, parallelize jobs, and fail fast on cheap gates.

On interviews: outline your pipeline stages and what each protects. Discuss required checks versus optional signal and how you debug failing jobs.

Common pitfalls: tests that pass locally but fail in CI due to env drift; secrets in logs; merging with bypassed checks during crunch.

The trade-off is flexibility versus complexity—know when the simpler path is enough.

Checklist:

• Mirror local scripts in CI commands.
• Mark required status checks on protected branches.
• Separate fast PR feedback from nightly heavy jobs.
• Keep CI config reviewed like application code.