From 8a903111edca013b64b61ea5c1c70ed2c2a060c4 Mon Sep 17 00:00:00 2001 From: ialdg <39755524+ialdg@users.noreply.github.com> Date: Sat, 30 Mar 2024 07:38:39 +0100 Subject: [PATCH 1/3] Update _packages_or_dependencies.md Hi. This modification proposal it's about removing a looping link. Regards. IL. --- website/snippets/_packages_or_dependencies.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/snippets/_packages_or_dependencies.md b/website/snippets/_packages_or_dependencies.md index 61014bc2b1a..e2069bb83b6 100644 --- a/website/snippets/_packages_or_dependencies.md +++ b/website/snippets/_packages_or_dependencies.md @@ -2,7 +2,9 @@ ## Use cases Starting from dbt v1.6, `dependencies.yml` has replaced `packages.yml`. The `dependencies.yml` file can now contain both types of dependencies: "package" and "project" dependencies. -- ["Package" dependencies](/docs/build/packages) lets you add source code from someone else's dbt project into your own, like a library. +- ["Package" dependencies](/docs/build/packages) lets you add source code from someone else's dbt project into your own, like a library. + + [comment]: Why add a link to this bulletpoint that redirects the reader to the same website? It makes no sense because it's a never ending loop. It's like having a website named "Make a meal", that has a list of bulletpoints like: "1- Buy it from a restaurant. 2- Make a meal" and the second bulletpoint sends the reader to itself. My proposal is to remove this looping link. Regards. - ["Project" dependencies](/docs/collaborate/govern/project-dependencies) provide a different way to build on top of someone else's work in dbt. If your dbt project doesn't require the use of Jinja within the package specifications, you can simply rename your existing `packages.yml` to `dependencies.yml`. However, something to note is if your project's package specifications use Jinja, particularly for scenarios like adding an environment variable or a [Git token method](/docs/build/packages#git-token-method) in a private Git package specification, you should continue using the `packages.yml` file name. From fb7c3b08a61d13f64731cd3576dbfa9a4732824d Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Tue, 9 Apr 2024 13:09:11 +0100 Subject: [PATCH 2/3] Update website/snippets/_packages_or_dependencies.md --- website/snippets/_packages_or_dependencies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/snippets/_packages_or_dependencies.md b/website/snippets/_packages_or_dependencies.md index e2069bb83b6..9efbad62a7e 100644 --- a/website/snippets/_packages_or_dependencies.md +++ b/website/snippets/_packages_or_dependencies.md @@ -2,7 +2,7 @@ ## Use cases Starting from dbt v1.6, `dependencies.yml` has replaced `packages.yml`. The `dependencies.yml` file can now contain both types of dependencies: "package" and "project" dependencies. -- ["Package" dependencies](/docs/build/packages) lets you add source code from someone else's dbt project into your own, like a library. +- ["Package" dependencies](/docs/build/packages#how-do-i-add-a-package-to-my-project) lets you add source code from someone else's dbt project into your own, like a library. [comment]: Why add a link to this bulletpoint that redirects the reader to the same website? It makes no sense because it's a never ending loop. It's like having a website named "Make a meal", that has a list of bulletpoints like: "1- Buy it from a restaurant. 2- Make a meal" and the second bulletpoint sends the reader to itself. My proposal is to remove this looping link. Regards. - ["Project" dependencies](/docs/collaborate/govern/project-dependencies) provide a different way to build on top of someone else's work in dbt. From 58d0b90242772ba8cd046bfefaef7af21b724d9e Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Tue, 9 Apr 2024 13:09:24 +0100 Subject: [PATCH 3/3] Update website/snippets/_packages_or_dependencies.md --- website/snippets/_packages_or_dependencies.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/snippets/_packages_or_dependencies.md b/website/snippets/_packages_or_dependencies.md index 9efbad62a7e..3cfcf7fbf11 100644 --- a/website/snippets/_packages_or_dependencies.md +++ b/website/snippets/_packages_or_dependencies.md @@ -4,7 +4,6 @@ Starting from dbt v1.6, `dependencies.yml` has replaced `packages.yml`. The `dependencies.yml` file can now contain both types of dependencies: "package" and "project" dependencies. - ["Package" dependencies](/docs/build/packages#how-do-i-add-a-package-to-my-project) lets you add source code from someone else's dbt project into your own, like a library. - [comment]: Why add a link to this bulletpoint that redirects the reader to the same website? It makes no sense because it's a never ending loop. It's like having a website named "Make a meal", that has a list of bulletpoints like: "1- Buy it from a restaurant. 2- Make a meal" and the second bulletpoint sends the reader to itself. My proposal is to remove this looping link. Regards. - ["Project" dependencies](/docs/collaborate/govern/project-dependencies) provide a different way to build on top of someone else's work in dbt. If your dbt project doesn't require the use of Jinja within the package specifications, you can simply rename your existing `packages.yml` to `dependencies.yml`. However, something to note is if your project's package specifications use Jinja, particularly for scenarios like adding an environment variable or a [Git token method](/docs/build/packages#git-token-method) in a private Git package specification, you should continue using the `packages.yml` file name.