-
Notifications
You must be signed in to change notification settings - Fork 984
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
Update mentions of dbt CLI #4356
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
website/docs/dbt-cli/cli-overview.md
Outdated
@@ -3,7 +3,7 @@ title: "CLI overview" | |||
description: "Run your dbt project from the command line." | |||
--- | |||
|
|||
dbt Core ships with a command-line interface (CLI) for running your dbt project. The dbt CLI is free to use and available as an [open source project](https://github.com/dbt-labs/dbt-core). | |||
dbt Core ships with a command-line interface (CLI) for running your dbt project. dbt Core and it's CLI are free to use and available as an [open source project](https://github.com/dbt-labs/dbt-core). |
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.
is this page referenced anywhere? if not, we should prob remove it because its one of those pages that's not even in the sidebar or anything https://docs.getdbt.com/dbt-cli/cli-overview
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.
It still gets hundreds of views a week so let me check with PM about whether we should remove it entirely or move this content elsewhere. I'll create a follow up PR based on their answer
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.
I agree we should remove it (and move content if we need to.) Maybe redirect it to https://docs.getdbt.com/docs/core/about-dbt-core ?
Also check if any docs link to it!
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.
@matthewshaver Just found a few places where I'd remove "CLI" but looks great! Thanks for spinning this up and helping to reduce confusion.
website/docs/dbt-cli/cli-overview.md
Outdated
@@ -3,7 +3,7 @@ title: "CLI overview" | |||
description: "Run your dbt project from the command line." | |||
--- | |||
|
|||
dbt Core ships with a command-line interface (CLI) for running your dbt project. The dbt CLI is free to use and available as an [open source project](https://github.com/dbt-labs/dbt-core). | |||
dbt Core ships with a command-line interface (CLI) for running your dbt project. dbt Core and it's CLI are free to use and available as an [open source project](https://github.com/dbt-labs/dbt-core). |
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.
I agree we should remove it (and move content if we need to.) Maybe redirect it to https://docs.getdbt.com/docs/core/about-dbt-core ?
Also check if any docs link to it!
@@ -76,7 +76,7 @@ You can recognize Jinja based on the delimiters the language uses, which we refe | |||
|
|||
When used in a dbt model, your Jinja needs to compile to a valid query. To check what SQL your Jinja compiles to: | |||
* **Using dbt Cloud:** Click the compile button to see the compiled SQL in the Compiled SQL pane | |||
* **Using the dbt CLI:** Run `dbt compile` from the command line. Then open the compiled SQL file in the `target/compiled/{project name}/` directory. Use a split screen in your code editor to keep both files open at once. | |||
* **Using the dbt Core CLI:** Run `dbt compile` from the command line. Then open the compiled SQL file in the `target/compiled/{project name}/` directory. Use a split screen in your code editor to keep both files open at once. |
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.
I'd remove CLI here because we say "command line" and it feels like core/cloud comparison
* **Using the dbt Core CLI:** Run `dbt compile` from the command line. Then open the compiled SQL file in the `target/compiled/{project name}/` directory. Use a split screen in your code editor to keep both files open at once. | |
* **Using the dbt Core:** Run `dbt compile` from the command line. Then open the compiled SQL file in the `target/compiled/{project name}/` directory. Use a split screen in your code editor to keep both files open at once. |
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.
Removing "the" as well in this case
@@ -9,7 +9,7 @@ If you'd like to work through this query, add [this CSV](https://github.com/dbt- | |||
|
|||
While working through the steps of this model, we recommend that you have your compiled SQL open as well, to check what your Jinja compiles to. To do this: | |||
* **Using dbt Cloud:** Click the compile button to see the compiled SQL in the right hand pane | |||
* **Using the dbt CLI:** Run `dbt compile` from the command line. Then open the compiled SQL file in the `target/compiled/{project name}/` directory. Use a split screen in your code editor to keep both files open at once. | |||
* **Using the dbt Core CLI:** Run `dbt compile` from the command line. Then open the compiled SQL file in the `target/compiled/{project name}/` directory. Use a split screen in your code editor to keep both files open at once. |
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.
This is redundant, so best to drop CLI
* **Using the dbt Core CLI:** Run `dbt compile` from the command line. Then open the compiled SQL file in the `target/compiled/{project name}/` directory. Use a split screen in your code editor to keep both files open at once. | |
* **Using the dbt Core:** Run `dbt compile` from the command line. Then open the compiled SQL file in the `target/compiled/{project name}/` directory. Use a split screen in your code editor to keep both files open at once. |
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.
Need to remove "the" in this case. Fixing in follow up coment
Co-authored-by: Leona B. Campbell <[email protected]>
Co-authored-by: Leona B. Campbell <[email protected]>
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.
Looks great!
Thank you @matthewshaver - I was confused about that too. |
What are you changing in this pull request and why?
Updates old mentions of
dbt CLI
to say eitherdbt Core
ordbt Core CLI
depending on the context.Checklist