From 90541a610d79f704664fc32bdaac2ca7e631c32d Mon Sep 17 00:00:00 2001 From: Jake Peterson <5532776+jpetey75@users.noreply.github.com> Date: Wed, 15 Apr 2026 12:52:26 +0200 Subject: [PATCH 1/2] Fix broken anchor links on automate-cli-workflow page MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The six "dev profiles" helper links pointed to an anchor on how-to-use-lightdash-preview that no longer exists — the section was consolidated into this page. Repoint them to #use-developer-credentials on the same page so users land on the right content. Co-Authored-By: Claude Opus 4.6 (1M context) --- guides/cli/automate-cli-workflow.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/guides/cli/automate-cli-workflow.mdx b/guides/cli/automate-cli-workflow.mdx index 83a8e9d8..53d7a5d2 100644 --- a/guides/cli/automate-cli-workflow.mdx +++ b/guides/cli/automate-cli-workflow.mdx @@ -46,7 +46,7 @@ Back in Lightdash, create a new personal access token, by going to `Settings` > * You might be able to copy a bunch of the information from your local `profiles.yml` file. You can see what's in there by typing `cat ~/.dbt/profiles.yml` in your terminal. * If you have a separate `prod` and `dev` profile, you probably want to use the information from your `prod` profile for your GitHub action. -* If you want to have different connection settings depending on the user that opened the pull request (dev profiles), then [check out this guide](/guides/cli/how-to-use-lightdash-preview#how-to-use-the-developer-credentials-in-your-preview-project). +* If you want to have different connection settings depending on the user that opened the pull request (dev profiles), then [check out this guide](#use-developer-credentials). Find your data warehouse from the list below to get a profiles.yml file template. Fill out this template, and this is your `DBT_PROFILES` secret. @@ -77,7 +77,7 @@ Find your data warehouse from the list below to get a profiles.yml file template Copy-paste this template into the secret and fill out the details. - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](/guides/cli/how-to-use-lightdash-preview#how-to-use-the-developer-credentials-in-your-preview-project). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). ```yaml [my-bigquery-db]: # this is the name of your project @@ -117,7 +117,7 @@ Find your data warehouse from the list below to get a profiles.yml file template More info in dbt's profiles docs: [https://docs.getdbt.com/reference/warehouse-profiles/postgres-profile#profile-configuration](https://docs.getdbt.com/reference/warehouse-profiles/postgres-profile#profile-configuration) - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](/guides/cli/how-to-use-lightdash-preview#how-to-use-the-developer-credentials-in-your-preview-project). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). @@ -143,7 +143,7 @@ Find your data warehouse from the list below to get a profiles.yml file template More info in dbt's profiles docs: [https://docs.getdbt.com/reference/warehouse-profiles/redshift-profile#password-based-authentication](https://docs.getdbt.com/reference/warehouse-profiles/redshift-profile#password-based-authentication) - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](/guides/cli/how-to-use-lightdash-preview#how-to-use-the-developer-credentials-in-your-preview-project). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). @@ -172,7 +172,7 @@ Find your data warehouse from the list below to get a profiles.yml file template More info in dbt's profiles docs: [https://docs.getdbt.com/reference/warehouse-profiles/snowflake-profile#user--password-authentication](https://docs.getdbt.com/reference/warehouse-profiles/snowflake-profile#user--password-authentication) - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](/guides/cli/how-to-use-lightdash-preview#how-to-use-the-developer-credentials-in-your-preview-project). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). @@ -199,7 +199,7 @@ Find your data warehouse from the list below to get a profiles.yml file template More info in dbt's profiles docs: [https://docs.getdbt.com/reference/warehouse-profiles/bigquery-profile#service-account-json](https://docs.getdbt.com/reference/warehouse-profiles/bigquery-profile#service-account-json) - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](/guides/cli/how-to-use-lightdash-preview#how-to-use-the-developer-credentials-in-your-preview-project). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). From 771096788bd64942b80e09cfaf446ba6c46d6055 Mon Sep 17 00:00:00 2001 From: Jake Peterson <5532776+jpetey75@users.noreply.github.com> Date: Fri, 17 Apr 2026 13:58:23 -0500 Subject: [PATCH 2/2] Point dev-profiles links to #use-profile-targets MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit #use-developer-credentials is a thin intro section (just an intro + an Info callout for dbt cloud IDE users). The concrete "what to add to your DBT_PROFILES secret" content — the multi-target YAML with per- developer outputs — lives one heading down in #use-profile-targets, which is what the link text actually promises. Co-Authored-By: Claude Opus 4.6 (1M context) --- guides/cli/automate-cli-workflow.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/guides/cli/automate-cli-workflow.mdx b/guides/cli/automate-cli-workflow.mdx index 53d7a5d2..63d4cee2 100644 --- a/guides/cli/automate-cli-workflow.mdx +++ b/guides/cli/automate-cli-workflow.mdx @@ -46,7 +46,7 @@ Back in Lightdash, create a new personal access token, by going to `Settings` > * You might be able to copy a bunch of the information from your local `profiles.yml` file. You can see what's in there by typing `cat ~/.dbt/profiles.yml` in your terminal. * If you have a separate `prod` and `dev` profile, you probably want to use the information from your `prod` profile for your GitHub action. -* If you want to have different connection settings depending on the user that opened the pull request (dev profiles), then [check out this guide](#use-developer-credentials). +* If you want to have different connection settings depending on the user that opened the pull request (dev profiles), then [check out this guide](#use-profile-targets). Find your data warehouse from the list below to get a profiles.yml file template. Fill out this template, and this is your `DBT_PROFILES` secret. @@ -77,7 +77,7 @@ Find your data warehouse from the list below to get a profiles.yml file template Copy-paste this template into the secret and fill out the details. - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-profile-targets). ```yaml [my-bigquery-db]: # this is the name of your project @@ -117,7 +117,7 @@ Find your data warehouse from the list below to get a profiles.yml file template More info in dbt's profiles docs: [https://docs.getdbt.com/reference/warehouse-profiles/postgres-profile#profile-configuration](https://docs.getdbt.com/reference/warehouse-profiles/postgres-profile#profile-configuration) - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-profile-targets). @@ -143,7 +143,7 @@ Find your data warehouse from the list below to get a profiles.yml file template More info in dbt's profiles docs: [https://docs.getdbt.com/reference/warehouse-profiles/redshift-profile#password-based-authentication](https://docs.getdbt.com/reference/warehouse-profiles/redshift-profile#password-based-authentication) - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-profile-targets). @@ -172,7 +172,7 @@ Find your data warehouse from the list below to get a profiles.yml file template More info in dbt's profiles docs: [https://docs.getdbt.com/reference/warehouse-profiles/snowflake-profile#user--password-authentication](https://docs.getdbt.com/reference/warehouse-profiles/snowflake-profile#user--password-authentication) - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-profile-targets). @@ -199,7 +199,7 @@ Find your data warehouse from the list below to get a profiles.yml file template More info in dbt's profiles docs: [https://docs.getdbt.com/reference/warehouse-profiles/bigquery-profile#service-account-json](https://docs.getdbt.com/reference/warehouse-profiles/bigquery-profile#service-account-json) - This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-developer-credentials). + This will always use this project connection in your GitHub actions. If you want your preview projects to have different connection settings depending on the user that opened the pull request (dev profiles), then see what you need to add to your secret [in this guide](#use-profile-targets).