0Pricing
SQL Academy · Lesson

CI for Schema Changes (GitHub Actions)

Run migrations, dbt build and SQLFluff lint inside GitHub Actions on every PR, with ephemeral databases.

Why CI for SQL?

Manual migrations cause outages. CI catches:

  • Migration that fails to apply
  • Migration that breaks existing tests
  • Schema drift between environments
  • Lint and test regressions

A Solid SQL CI Pipeline

  1. Spin up ephemeral Postgres (Docker / GitHub Actions service)
  2. Apply all migrations from scratch
  3. Apply only the new migrations on a copy of staging schema
  4. Run dbt build / Flyway test / app tests
  5. SQLFluff lint
  6. Schema diff report

All lessons in this course

  1. DBT (Data Build Tool) Fundamentals
  2. SQLFluff and Linting
  3. Testing SQL: dbt tests, Great Expectations
  4. CI for Schema Changes (GitHub Actions)
← Back to SQL Academy