feat: Make dbt provider default to current directory when nothing specified#36
Merged
Merged
Conversation
jvanbuel
approved these changes
May 26, 2026
CasperTeirlinck
force-pushed
the
feat/checkup-dbt-default-path
branch
from
6506ce7 to
e4f2416
Compare
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
2 participants
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.
When running
checkup runin a project in a monorepo with a commoncheckup.yaml, you can't set the project_dir or manifest_path arguments to the dbt provider in the yaml. To avoid having to provide this via cmline arguments or adding a checkup yaml to the project folder just for this, I think it makes sense to make the dbt provider default to the current directory instead of throwing an error.