From cfd3f8492606ac25cbaa5cf55287092f651886f0 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 21 Nov 2023 17:44:20 -0500 Subject: [PATCH] Apply suggestions from code review --- website/docs/reference/commands/deps.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/reference/commands/deps.md b/website/docs/reference/commands/deps.md index ddd3e4acb8e..40d9ee1cabd 100644 --- a/website/docs/reference/commands/deps.md +++ b/website/docs/reference/commands/deps.md @@ -65,8 +65,8 @@ dbt generates the `package-lock.yml` file in the _project_root_ where `packages. When you update the package spec and run `dbt deps` again, the `package-lock.yml` and `packages.yml` files update accordingly. There are two flags related to `package-lock.yml`: -- `dbt deps --upgrade` — creates or updates the `package-lock.yml` with the most recent dependencies from `packages.yml` and installs them. -- `dbt deps --lock` — creates or updates the `package-lock.yml` but does not install the packages. +- `dbt deps --upgrade` — creates or updates the `package-lock.yml` file with the most recent dependencies from `packages.yml` and installs them. +- `dbt deps --lock` — creates or updates the `package-lock.yml` file but does not install the packages. The `--add-package` flag allows you to add a package to the `packages.yml` with configurable `--version` and `--source` information. The `--dry-run` flag, when set to `False`(default), recompiles the `package-lock.yml` file after a new package is added to the `packages.yml` file. Set the flag to `True` for the changes to not persist.