Turbo CI FAQ

Why does Turbo CI build a model my pull request didn't change?

Turbo CI runs on your pull request’s latest commit, exactly as you pushed it. Commands that select with state:modified (or a sub-selector such as state:modified.body) compare each file in that commit with the manifest.json of the schedule you defer to, which usually runs on your default branch. A model counts as modified whenever its file differs from that manifest, not only when your pull request changed it.So if your default branch changes a model after your branch last merged it, your branch still has the older copy of that model. The file differs from the manifest, and Turbo CI builds the model even though your pull request’s list of changed files doesn’t include it.To confirm, compare the file on your branch with the default branch, then with your pull request’s own changes:

# Your branch against the default branch: shows a difference
git diff origin/main HEAD -- path/to/model.sql

# Only the changes your pull request made: shows nothing
git diff origin/main...HEAD -- path/to/model.sql

To fix it, merge your default branch into your branch, or rebase onto it, and push. The next Turbo CI run compares matching files and skips the model.

Schedule Anatomy

Deploy Schedules

Managing Schedules

CI/CD

What Turbo CI builds

​What Turbo CI builds

What Turbo CI builds