Because running our dbt transformations takes time and resources on the destination, we only trigger the entirety of our transformations once a day in our deployment.yml. (We have a more limited set of actions scheduled to run more frequently.) Most of the time, they do nothing because nothing has changed in our dbt setup; this is a waste of both our resources at the destination and yours. What would be great is if we could set up a run-of-the mill GitHub hook when we commit something to a particular branch (master) that triggers dbt to run on demand.
Please sign in to leave a comment.