Ship dbt_project.yml; drop dbt init from Task 1#4
Merged
Conversation
The template is now a ready-to-run dbt project. Students no longer run `dbt init` and clean up its example scaffolding (the #1 autograder footgun: leftover models/example -> FAIL not_null_my_first_dbt_model_id). - add dbt_project.yml (staging = view, marts = table), matching the profiles.yml.example profile name. - README: Task 1 is now "connect to the shared database"; file tree no longer marks dbt_project.yml as "NOT included". - dbt-parse CI: dbt_project.yml now always ships, so parse always runs. Verified `dbt deps && dbt parse` is green against the raw stubs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Situation
The Week 10 assignment template shipped every support file except
dbt_project.yml. Task 1 asked students to rundbt initin a throwaway subfolder, move the generateddbt_project.ymlup, delete the rest, then hand-edit it to strip theexample:block.Problem
That step was the #1 autograder footgun: any leftover
models/example/my_first_dbt_model.sqlmakesdbt buildreportFAIL 1 not_null_my_first_dbt_model_idand blocks theERROR=0requirement. It also taught a distorted version of the real workflow (dbt initnormally scaffolds a project in place, not a delete-the-rest dance).Solution
Ship a ready-to-run
dbt_project.ymlso students fill in stubs instead of scaffolding.dbt_project.yml—staging=view,marts=table,profile: nyc_taxi_borough_daily(matchesprofiles.yml.example).profiles.yml+dbt debug); file tree no longer marksdbt_project.ymlas NOT included.dbt-parseCI —dbt_project.ymlnow always ships, so parse always runs. Verifieddbt deps && dbt parseis green against the raw TODO stubs.Paired with curriculum edits in the datatrack repo (assignment Task 1, Ch2 forward-reference, rubric, lesson plan).