Thoughts on putting all the dbt sub-projects into 1 directory instead of them all living in the root dir?
Will be better to keep the overview when we scale to multiples of them.

I don't have a super strong opinion on this but we making that change in the future should be straightforward. I think it depends a bit on what the root dir looks like later

@aalan3 agree it comes down to preference/opinion. I do think having both the core spellbook dbt directories (seeds/scripts/macros/...) and the subproject directories (tokens/ spellbook-daily/..) scattered on the same dir level will be confusing for new contributors.

Yeah that makes sense, I think the seeds/scripts/macros should go into something like shared eventually.

i think we should move forward with the directory structure organization now while we're in the weeds here. it also helps with a few suggestions to the code i have in this PR.

• root directory
  • spellbook_projects
    • spellbook_daily
      • dbt_project.yml
      • profiles.yml
      • packages.yml
      • package_lock.yml
      • models/
      • tests/
      • seeds/
    • tokens
      • dbt_project.yml
      • profiles.yml
      • packages.yml
      • package_lock.yml
      • models/
      • tests/
      • seeds/
    • dex
      • dbt_project.yml
      • profiles.yml
      • packages.yml
      • package_lock.yml
      • models/
      • tests/
      • seeds/
    • ...future sub projects
    • macros/
    • sources/
• docs/
• scripts/
• .github/
• ....and others needed to remain here

we haven't tried moving tests/seeds into subprojects yet, but that is because we've only done tokens and there weren't any to move with the models. i think it'll make sense to have those project specific, but we can be lenient to move back a level with macros/sources if it demands it.

then with this structure, we can simplify the CI here to use paths: and specify one subproject path, rather than path-ignores on all other subprojects. that could grow out of hand potentially.

maybe this means we need to move the two PRs back into one, to make it all work? or at least fast follow to merge one after the other and be prepared to ensure it all works.

I don't think we should do this now and in the context of this PR @jeff-dude. Lets merge this and test the new sub project and after that we can move things around in the repo if we want. Right now the benefit to CI structure is not that much since we only have 2 sub projects.

I don't think we should do this now and in the context of this PR @jeff-dude. Lets merge this and test the new sub project and after that we can move things around in the repo if we want. Right now the benefit to CI structure is not that much since we only have 2 sub projects.

makes sense, but let's remember this comment in future cleanup