From 7d75a6d704b1a8cb636e023ac46c941df3d01c72 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 21 Mar 2024 12:18:01 +0000 Subject: [PATCH 1/8] revert code fix --- website/docs/guides/bigquery-qs.md | 75 +++++++++++++++++++++- website/docs/guides/databricks-qs.md | 74 ++++++++++++++++++++- website/docs/guides/microsoft-fabric-qs.md | 73 ++++++++++++++++++++- website/docs/guides/redshift-qs.md | 74 ++++++++++++++++++++- website/docs/guides/snowflake-qs.md | 74 ++++++++++++++++++++- website/docs/guides/starburst-galaxy-qs.md | 68 +++++++++++++++++++- 6 files changed, 426 insertions(+), 12 deletions(-) diff --git a/website/docs/guides/bigquery-qs.md b/website/docs/guides/bigquery-qs.md index 50a7e2d7183..6f6643ffcad 100644 --- a/website/docs/guides/bigquery-qs.md +++ b/website/docs/guides/bigquery-qs.md @@ -111,9 +111,80 @@ Now that you have a repository configured, you can initialize your project and s ## Build your first model -import BuildFirstModel from '/snippets/quickstarts/_build-your-first-model.md'; +You have two options for working with files in the dbt Cloud IDE: - +- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. + +- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. + +Name the new branch `add-customers-model`. + +1. Click the **...** next to the `models` directory, then select **Create file**. +2. Name the file `customers.sql`, then click **Create**. +3. Copy the following query into the file and click **Save**. + + +```sql +with customers as ( + + select + id as customer_id, + first_name, + last_name + + from `dbt-tutorial`.jaffle_shop.customers + +), + +orders as ( + + select + id as order_id, + user_id as customer_id, + order_date, + status + + from `dbt-tutorial`.jaffle_shop.orders + +), + +customer_orders as ( + + select + customer_id, + + min(order_date) as first_order_date, + max(order_date) as most_recent_order_date, + count(order_id) as number_of_orders + + from orders + + group by 1 + +), + +final as ( + + select + customers.customer_id, + customers.first_name, + customers.last_name, + customer_orders.first_order_date, + customer_orders.most_recent_order_date, + coalesce(customer_orders.number_of_orders, 0) as number_of_orders + + from customers + + left join customer_orders using (customer_id) + +) + +select * from final +``` + +4. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run and see the three models. + +Later, you can connect your business intelligence (BI) tools to these views and tables so they only read cleaned up data rather than raw data in your BI tool. #### FAQs diff --git a/website/docs/guides/databricks-qs.md b/website/docs/guides/databricks-qs.md index 8141deba3bb..17010f5f259 100644 --- a/website/docs/guides/databricks-qs.md +++ b/website/docs/guides/databricks-qs.md @@ -190,9 +190,79 @@ Now that you have a repository configured, you can initialize your project and s ## Build your first model -import BuildFirstModel from '/snippets/quickstarts/_build-your-first-model.md'; +You have two options for working with files in the dbt Cloud IDE: - +- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. + +- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. + +Name the new branch `add-customers-model`. + +1. Click the **...** next to the `models` directory, then select **Create file**. +2. Name the file `customers.sql`, then click **Create**. +3. Copy the following query into the file and click **Save**. + +```sql +with customers as ( + + select + id as customer_id, + first_name, + last_name + + from jaffle_shop_customers + +), + +orders as ( + + select + id as order_id, + user_id as customer_id, + order_date, + status + + from jaffle_shop_orders + +), + +customer_orders as ( + + select + customer_id, + + min(order_date) as first_order_date, + max(order_date) as most_recent_order_date, + count(order_id) as number_of_orders + + from orders + + group by 1 + +), + +final as ( + + select + customers.customer_id, + customers.first_name, + customers.last_name, + customer_orders.first_order_date, + customer_orders.most_recent_order_date, + coalesce(customer_orders.number_of_orders, 0) as number_of_orders + + from customers + + left join customer_orders using (customer_id) + +) + +select * from final +``` + +4. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run and see the three models. + +Later, you can connect your business intelligence (BI) tools to these views and tables so they only read cleaned up data rather than raw data in your BI tool. #### FAQs diff --git a/website/docs/guides/microsoft-fabric-qs.md b/website/docs/guides/microsoft-fabric-qs.md index 16fe3b6320f..a598e405886 100644 --- a/website/docs/guides/microsoft-fabric-qs.md +++ b/website/docs/guides/microsoft-fabric-qs.md @@ -133,9 +133,78 @@ Now that you have a repository configured, you can initialize your project and s ## Build your first model -import BuildFirstModel from '/snippets/quickstarts/_build-your-first-model.md'; +You have two options for working with files in the dbt Cloud IDE: - +- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. + +- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. + +Name the new branch `add-customers-model`. + +1. Click the **...** next to the `models` directory, then select **Create file**. +2. Name the file `customers.sql`, then click **Create**. +3. Copy the following query into the file and click **Save**. + + + + ```sql + with customers as ( + + select + ID as customer_id, + FIRST_NAME as first_name, + LAST_NAME as last_name + + from dbo.customers + ), + + orders as ( + + select + ID as order_id, + USER_ID as customer_id, + ORDER_DATE as order_date, + STATUS as status + + from dbo.orders + ), + + customer_orders as ( + + select + customer_id, + + min(order_date) as first_order_date, + max(order_date) as most_recent_order_date, + count(order_id) as number_of_orders + + from orders + + group by customer_id + ), + + final as ( + + select + customers.customer_id, + customers.first_name, + customers.last_name, + customer_orders.first_order_date, + customer_orders.most_recent_order_date, + coalesce(customer_orders.number_of_orders, 0) as number_of_orders + + from customers + + left join customer_orders on customers.customer_id = customer_orders.customer_id + ) + + select * from final + ``` + + +4. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run and see the three models. + +Later, you can connect your business intelligence (BI) tools to these views and tables so they only read cleaned up data rather than raw data in your BI tool. #### FAQs diff --git a/website/docs/guides/redshift-qs.md b/website/docs/guides/redshift-qs.md index bf324f73e92..ffa685f47ba 100644 --- a/website/docs/guides/redshift-qs.md +++ b/website/docs/guides/redshift-qs.md @@ -203,9 +203,79 @@ Now that you have a repository configured, you can initialize your project and s ## Build your first model -import BuildFirstModel from '/snippets/quickstarts/_build-your-first-model.md'; +You have two options for working with files in the dbt Cloud IDE: - +- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. + +- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. + +Name the new branch `add-customers-model`. + +1. Click the **...** next to the `models` directory, then select **Create file**. +2. Name the file `customers.sql`, then click **Create**. +3. Copy the following query into the file and click **Save**. + +```sql +with customers as ( + + select + id as customer_id, + first_name, + last_name + + from jaffle_shop.customers + +), + +orders as ( + + select + id as order_id, + user_id as customer_id, + order_date, + status + + from jaffle_shop.orders + +), + +customer_orders as ( + + select + customer_id, + + min(order_date) as first_order_date, + max(order_date) as most_recent_order_date, + count(order_id) as number_of_orders + + from orders + + group by 1 + +), + +final as ( + + select + customers.customer_id, + customers.first_name, + customers.last_name, + customer_orders.first_order_date, + customer_orders.most_recent_order_date, + coalesce(customer_orders.number_of_orders, 0) as number_of_orders + + from customers + + left join customer_orders using (customer_id) + +) + +select * from final +``` + +4. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run and see the three models. + +Later, you can connect your business intelligence (BI) tools to these views and tables so they only read cleaned up data rather than raw data in your BI tool. #### FAQs diff --git a/website/docs/guides/snowflake-qs.md b/website/docs/guides/snowflake-qs.md index 3c12a8c5acd..37dae950a11 100644 --- a/website/docs/guides/snowflake-qs.md +++ b/website/docs/guides/snowflake-qs.md @@ -229,9 +229,79 @@ Now that you have a repository configured, you can initialize your project and s ## Build your first model -import BuildFirstModel from '/snippets/quickstarts/_build-your-first-model.md'; +You have two options for working with files in the dbt Cloud IDE: - +- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. + +- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. + +Name the new branch `add-customers-model`. + +1. Click the **...** next to the `models` directory, then select **Create file**. +2. Name the file `customers.sql`, then click **Create**. +3. Copy the following query into the file and click **Save**. + +```sql +with customers as ( + + select + id as customer_id, + first_name, + last_name + + from raw.jaffle_shop.customers + +), + +orders as ( + + select + id as order_id, + user_id as customer_id, + order_date, + status + + from raw.jaffle_shop.orders + +), + +customer_orders as ( + + select + customer_id, + + min(order_date) as first_order_date, + max(order_date) as most_recent_order_date, + count(order_id) as number_of_orders + + from orders + + group by 1 + +), + +final as ( + + select + customers.customer_id, + customers.first_name, + customers.last_name, + customer_orders.first_order_date, + customer_orders.most_recent_order_date, + coalesce(customer_orders.number_of_orders, 0) as number_of_orders + + from customers + + left join customer_orders using (customer_id) + +) + +select * from final +``` + +4. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run and see the three models. + +Later, you can connect your business intelligence (BI) tools to these views and tables so they only read cleaned up data rather than raw data in your BI tool. ## Change the way your model is materialized diff --git a/website/docs/guides/starburst-galaxy-qs.md b/website/docs/guides/starburst-galaxy-qs.md index 0c58766884d..5a78961abb5 100644 --- a/website/docs/guides/starburst-galaxy-qs.md +++ b/website/docs/guides/starburst-galaxy-qs.md @@ -232,9 +232,73 @@ Now that you have a repository configured, you can initialize your project and s ## Build your first model -import BuildFirstModel from '/snippets/quickstarts/_build-your-first-model.md'; +You have two options for working with files in the dbt Cloud IDE: - +- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. + +- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. + +Name the new branch `add-customers-model`. + +1. Click the **...** next to the `models` directory, then select **Create file**. +2. Name the file `customers.sql`, then click **Create**. +3. Copy the following query into the file and click **Save**. + +```sql +with customers as ( + + select + id as customer_id, + first_name, + last_name + + from dbt_quickstart.jaffle_shop.jaffle_shop_customers +), + +orders as ( + + select + id as order_id, + user_id as customer_id, + order_date, + status + + from dbt_quickstart.jaffle_shop.jaffle_shop_orders +), + + +customer_orders as ( + + select + customer_id, + min(order_date) as first_order_date, + max(order_date) as most_recent_order_date, + count(order_id) as number_of_orders + + from orders + group by 1 +), + +final as ( + + select + customers.customer_id, + customers.first_name, + customers.last_name, + customer_orders.first_order_date, + customer_orders.most_recent_order_date, + coalesce(customer_orders.number_of_orders, 0) as number_of_orders + + from customers + left join customer_orders on customers.customer_id = customer_orders.customer_id +) +select * from final + +``` + +4. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run and see the three models. + +Later, you can connect your business intelligence (BI) tools to these views and tables so they only read cleaned up data rather than raw data in your BI tool. #### FAQs From 743c141dffb7b91cd8b499c1b2f3721f08c45818 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 21 Mar 2024 12:18:26 +0000 Subject: [PATCH 2/8] remove snippet --- .../quickstarts/_build-your-first-model.md | 73 ------------------- 1 file changed, 73 deletions(-) delete mode 100644 website/snippets/quickstarts/_build-your-first-model.md diff --git a/website/snippets/quickstarts/_build-your-first-model.md b/website/snippets/quickstarts/_build-your-first-model.md deleted file mode 100644 index 4e447c743cc..00000000000 --- a/website/snippets/quickstarts/_build-your-first-model.md +++ /dev/null @@ -1,73 +0,0 @@ -You have two options for working with files in the dbt Cloud IDE: - -- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. - -- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. - -Name the new branch `add-customers-model`. - -1. Click the **...** next to the `models` directory, then select **Create file**. -2. Name the file `customers.sql`, then click **Create**. -3. Copy the following query into the file and click **Save**. - -```sql -with customers as ( - - select - id as customer_id, - first_name, - last_name - - from raw.jaffle_shop.customers - -), - -orders as ( - - select - id as order_id, - user_id as customer_id, - order_date, - status - - from raw.jaffle_shop.orders - -), - -customer_orders as ( - - select - customer_id, - - min(order_date) as first_order_date, - max(order_date) as most_recent_order_date, - count(order_id) as number_of_orders - - from orders - - group by 1 - -), - -final as ( - - select - customers.customer_id, - customers.first_name, - customers.last_name, - customer_orders.first_order_date, - customer_orders.most_recent_order_date, - coalesce(customer_orders.number_of_orders, 0) as number_of_orders - - from customers - - left join customer_orders using (customer_id) - -) - -select * from final -``` - -4. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run and see the three models. - -Later, you can connect your business intelligence (BI) tools to these views and tables so they only read cleaned up data rather than raw data in your BI tool. From 08035edd0df3b68381c850432dddea9584899a96 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 22 Mar 2024 14:22:11 +0000 Subject: [PATCH 3/8] Update bigquery-qs.md --- website/docs/guides/bigquery-qs.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/docs/guides/bigquery-qs.md b/website/docs/guides/bigquery-qs.md index 6f6643ffcad..8dbcf24c91a 100644 --- a/website/docs/guides/bigquery-qs.md +++ b/website/docs/guides/bigquery-qs.md @@ -113,9 +113,8 @@ Now that you have a repository configured, you can initialize your project and s You have two options for working with files in the dbt Cloud IDE: -- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. - -- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Create a new branch (recommended) — Create a new branch to edit and commit your changes. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Edit in the protected primary branch — If you prefer to edit, format, or lint files and execute dbt commands directly in your primary git branch. The dbt Cloud IDE prevents commits to the protected branch, so you will be prompted to commit your changes to a new branch. Name the new branch `add-customers-model`. From 811e6bc160b9cce469bdb231007d0bad57e307ce Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 22 Mar 2024 14:23:48 +0000 Subject: [PATCH 4/8] Update databricks-qs.md --- website/docs/guides/databricks-qs.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/docs/guides/databricks-qs.md b/website/docs/guides/databricks-qs.md index 17010f5f259..848ee19c59a 100644 --- a/website/docs/guides/databricks-qs.md +++ b/website/docs/guides/databricks-qs.md @@ -192,9 +192,8 @@ Now that you have a repository configured, you can initialize your project and s You have two options for working with files in the dbt Cloud IDE: -- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. - -- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Create a new branch (recommended) — Create a new branch to edit and commit your changes. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Edit in the protected primary branch — If you prefer to edit, format, or lint files and execute dbt commands directly in your primary git branch. The dbt Cloud IDE prevents commits to the protected branch, so you will be prompted to commit your changes to a new branch. Name the new branch `add-customers-model`. From b2a374336521ddb50e1748b360c1fca703312b91 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 22 Mar 2024 14:24:20 +0000 Subject: [PATCH 5/8] Update microsoft-fabric-qs.md --- website/docs/guides/microsoft-fabric-qs.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/docs/guides/microsoft-fabric-qs.md b/website/docs/guides/microsoft-fabric-qs.md index a598e405886..9189e126e7c 100644 --- a/website/docs/guides/microsoft-fabric-qs.md +++ b/website/docs/guides/microsoft-fabric-qs.md @@ -135,9 +135,8 @@ Now that you have a repository configured, you can initialize your project and s You have two options for working with files in the dbt Cloud IDE: -- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. - -- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Create a new branch (recommended) — Create a new branch to edit and commit your changes. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Edit in the protected primary branch — If you prefer to edit, format, or lint files and execute dbt commands directly in your primary git branch. The dbt Cloud IDE prevents commits to the protected branch, so you will be prompted to commit your changes to a new branch. Name the new branch `add-customers-model`. From b2a5cc670fe3e650a9fe9a0905c32c16ea2032eb Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 22 Mar 2024 14:24:52 +0000 Subject: [PATCH 6/8] Update redshift-qs.md --- website/docs/guides/redshift-qs.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/docs/guides/redshift-qs.md b/website/docs/guides/redshift-qs.md index ffa685f47ba..0d18d3c5d84 100644 --- a/website/docs/guides/redshift-qs.md +++ b/website/docs/guides/redshift-qs.md @@ -205,9 +205,8 @@ Now that you have a repository configured, you can initialize your project and s You have two options for working with files in the dbt Cloud IDE: -- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. - -- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Create a new branch (recommended) — Create a new branch to edit and commit your changes. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Edit in the protected primary branch — If you prefer to edit, format, or lint files and execute dbt commands directly in your primary git branch. The dbt Cloud IDE prevents commits to the protected branch, so you will be prompted to commit your changes to a new branch. Name the new branch `add-customers-model`. From d2dc791a1c8e4b8693df71a6d9105eeebe732229 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 22 Mar 2024 14:25:09 +0000 Subject: [PATCH 7/8] Update snowflake-qs.md --- website/docs/guides/snowflake-qs.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/docs/guides/snowflake-qs.md b/website/docs/guides/snowflake-qs.md index 37dae950a11..6d8a4494285 100644 --- a/website/docs/guides/snowflake-qs.md +++ b/website/docs/guides/snowflake-qs.md @@ -231,9 +231,8 @@ Now that you have a repository configured, you can initialize your project and s You have two options for working with files in the dbt Cloud IDE: -- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. - -- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Create a new branch (recommended) — Create a new branch to edit and commit your changes. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Edit in the protected primary branch — If you prefer to edit, format, or lint files and execute dbt commands directly in your primary git branch. The dbt Cloud IDE prevents commits to the protected branch, so you will be prompted to commit your changes to a new branch. Name the new branch `add-customers-model`. From 9d7e4cb4ed6ffb8d4ce0997d8045b7fee4ec8e1d Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 22 Mar 2024 14:25:21 +0000 Subject: [PATCH 8/8] Update starburst-galaxy-qs.md --- website/docs/guides/starburst-galaxy-qs.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/docs/guides/starburst-galaxy-qs.md b/website/docs/guides/starburst-galaxy-qs.md index 5a78961abb5..080b6d9f411 100644 --- a/website/docs/guides/starburst-galaxy-qs.md +++ b/website/docs/guides/starburst-galaxy-qs.md @@ -234,9 +234,8 @@ Now that you have a repository configured, you can initialize your project and s You have two options for working with files in the dbt Cloud IDE: -- Edit in the protected primary branch — Edit, format, or lint files and execute dbt commands directly in your primary git branch. Since the dbt Cloud IDE prevents commits to the protected branch, it prompts you to commit those changes to a new branch. - -- Create a new branch before editing — If you prefer to keep the primary branch unchanged, create a new branch before starting your edits. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Create a new branch (recommended) — Create a new branch to edit and commit your changes. Navigate to **Version Control** on the left sidebar and click **Create branch**. +- Edit in the protected primary branch — If you prefer to edit, format, or lint files and execute dbt commands directly in your primary git branch. The dbt Cloud IDE prevents commits to the protected branch, so you will be prompted to commit your changes to a new branch. Name the new branch `add-customers-model`.