MLOps Academy
Back to Development Environment

Continuous Integration

Automate tests, quality checks, and safe merges for ML codebases.

What CI should do
Make “merge” the safe default
  • Run on every PR and on main: lint, typecheck, tests, and a minimal build.
  • Fail fast with clear logs (so developers fix issues quickly).
  • Gate merges on required checks (branch protection).
  • Produce artifacts when useful (test reports, coverage, build outputs).
PR policy (simple and effective)
  • At least 1 approval for PRs
  • All required checks must pass
  • No direct pushes to main
  • Squash merge (optional) to keep history clean