Brief comments on the purpose of your changes:
For Dune Engine V2 I've checked that:
- I tested the query on dune.com after compiling the model with dbt compile (compiled queries are written to the target directory)
- I used "refs" to reference other models in this repo and "sources" to reference raw or decoded tables
- if adding a new model, I added a test
- the filename is unique and ends with .sql
- each sql file is a select statement and has only one view, table or function defined
- column names are
lowercase_snake_cased
When you are ready for a review, tag duneanalytics/data-experience. We will re-open your forked pull request as an internal pull request. Then your spells will run in dbt and the logs will be avaiable in Github Actions DBT Slim CI. This job will only run the models and tests changed by your PR compared to the production project.