-
Notifications
You must be signed in to change notification settings - Fork 969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds ls troubleshooting tips #5266
Adds ls troubleshooting tips #5266
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Co-authored-by: Mirna Wong <[email protected]>
Co-authored-by: Mirna Wong <[email protected]>
this looks brilliant @will-sargent-dbtlabs , thank you so much! preview here: https://docs-getdbt-7nc6j3cyp-dbt-labs.vercel.app/reference/node-selection/syntax#troubleshoot-with-the-ls-command |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢 and ready to merge! happy to get @dbeatty10 's feedback before merging 🙏 thank you team!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ok going to merge this for you @will-sargent-dbtlabs ! we can come back to update it if needed. thank you so much! |
What are you changing in this pull request and why?
The
dbt ls
command has been a personal goldmine find in helping to debug selectors and complex state:modified problems.I wanted to get this documented for others to see examples of how it can be used for this purpose. We do call out the command as an option in the table of commands, but there aren't any examples of how and why you might want to use it, and I believe it's arguably the best tool for troubleshooting this stuff, as it works in both the IDE and in jobs for logging.
Checklist