You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* update PR template
* added a few more performance related conditions
* remove text to tag data experience team
access issues for users to tag the group
* break out checks into groups
separate general checks, join checks, incremental checks
Copy file name to clipboardexpand all lines: pull_request_template.md
+12-2
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,22 @@ Brief comments on the purpose of your changes:
3
3
4
4
*For Dune Engine V2*
5
5
I've checked that:
6
-
6
+
General checks:
7
7
*[ ] I tested the query on dune.com after compiling the model with dbt compile (compiled queries are written to the target directory)
8
8
*[ ] I used "refs" to reference other models in this repo and "sources" to reference raw or decoded tables
9
9
*[ ] if adding a new model, I added a test
10
10
*[ ] the filename is unique and ends with .sql
11
11
*[ ] each sql file is a select statement and has only one view, table or function defined
12
12
*[ ] column names are `lowercase_snake_cased`
13
+
*[ ] if adding a new model, I edited the dbt project YAML file with new directory path for both models and seeds (if applicable)
14
+
*[ ] if adding a new model, I edited the alter table macro to display new database object (table or view) in UI explorer
15
+
*[ ] if adding a new materialized table, I edited the optimize table macro
16
+
17
+
Join logic:
18
+
*[ ] if joining to base table (i.e. ethereum transactions or traces), I looked to make it an inner join if possible
13
19
14
-
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.
20
+
Incremental logic:
21
+
*[ ] I used is_incremental & not is_incremental jinja block filters on both base tables and decoded tables
*[ ] if joining to base table (i.e. ethereum transactions or traces), I applied join condition where block_time >= date_trunc("day", now() - interval '1 week')
24
+
*[ ] if joining to prices view, I applied join condition where minute >= date_trunc("day", now() - interval '1 week')
0 commit comments