From d1dea5e690436ea0c3c1126795979dbeac4bf309 Mon Sep 17 00:00:00 2001 From: richardgourley Date: Wed, 15 Nov 2023 20:38:14 +0100 Subject: [PATCH 1/3] Removed repeated line of text. --- website/docs/terms/data-wrangling.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/docs/terms/data-wrangling.md b/website/docs/terms/data-wrangling.md index 4a26507adfd..58034fe8e91 100644 --- a/website/docs/terms/data-wrangling.md +++ b/website/docs/terms/data-wrangling.md @@ -37,7 +37,6 @@ Structuring your data is a type of transformation that involves reformatting and - Is your data in the format you need to perform analysis on it? Does your data need to be potentially unnested? *Should you nest or objectize columns together?* - Do the column names and values look correct for your use case? -Do the column names and values look correct for your use case? If your data is not in a format that is usable, you can look into different solutions such as pivoting or using different functions to unpack lists and JSON files so that they are in a tabular format. Pivoting is helpful because it allows you to change the way your dataset is structured by rearranging the way columns, rows, and their values are displayed. dbt has a [pre-built macro](https://github.com/dbt-labs/dbt-utils/blob/main/macros/sql/pivot.sql) that makes pivoting less of a headache and more of a breeze. From 8694388caee89cd716e5950d07a8aba594ff25ac Mon Sep 17 00:00:00 2001 From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com> Date: Wed, 15 Nov 2023 16:18:35 -0700 Subject: [PATCH 2/3] Fix config example for `dbt_project.yml` (#4443) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Previews - [Semantic models](https://docs-getdbt-com-git-dbeatty-semantic-model-conf-4886b9-dbt-labs.vercel.app/docs/build/semantic-models) ## What are you changing in this pull request and why? Within `dbt_project.yml`, resource types have dashes (`-`) instead of underscores (`_`), so we need to update this code example accordingly. ### Backstory Within the description for https://github.com/dbt-labs/docs.getdbt.com/issues/4180, I added some examples of what I _guessed_ the syntax would be, but I didn't specify that these were completely unverified guesses 😬. This particular example got missed during #4281. ### 🎩 image ## Checklist - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines. - [x] I have verified that the code examples work - [x] I have checked that the preview renders correctly --------- Co-authored-by: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> --- website/docs/docs/build/semantic-models.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/docs/docs/build/semantic-models.md b/website/docs/docs/build/semantic-models.md index 118e93a26b1..99ccef237f9 100644 --- a/website/docs/docs/build/semantic-models.md +++ b/website/docs/docs/build/semantic-models.md @@ -123,14 +123,18 @@ semantic_models: config: enabled: true | false group: some_group + meta: + some_key: some_value ``` Semantic model config in `dbt_project.yml`: ```yml -semantic_models: +semantic-models: my_project_name: +enabled: true | false +group: some_group + +meta: + some_key: some_value ``` From 39ddb79244c38090d32993978d67476826589679 Mon Sep 17 00:00:00 2001 From: Ly Nguyen Date: Wed, 15 Nov 2023 15:41:29 -0800 Subject: [PATCH 3/3] Update prereqs for CI and GitLab --- website/docs/docs/deploy/ci-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/deploy/ci-jobs.md b/website/docs/docs/deploy/ci-jobs.md index 6114ed1ca14..149a6951fdc 100644 --- a/website/docs/docs/deploy/ci-jobs.md +++ b/website/docs/docs/deploy/ci-jobs.md @@ -15,7 +15,7 @@ dbt Labs recommends that you create your CI job in a dedicated dbt Cloud [deploy - You have a dbt Cloud account. - For the [Concurrent CI checks](/docs/deploy/continuous-integration#concurrent-ci-checks) and [Smart cancellation of stale builds](/docs/deploy/continuous-integration#smart-cancellation) features, your dbt Cloud account must be on the [Team or Enterprise plan](https://www.getdbt.com/pricing/). - You must be connected using dbt Cloud’s native Git integration with [GitHub](/docs/cloud/git/connect-github), [GitLab](/docs/cloud/git/connect-gitlab), or [Azure DevOps](/docs/cloud/git/connect-azure-devops). - - If you’re using GitLab, you must use a paid or self-hosted account which includes support for GitLab webhooks. + - With GitLab, you need a paid or self-hosted account which includes support for GitLab webhooks and [project access tokens](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html). With GitLab Free, merge requests will invoke CI jobs but CI status updates (success or failure of the job) will not be reported back to GitLab. - If you previously configured your dbt project by providing a generic git URL that clones using SSH, you must reconfigure the project to connect through dbt Cloud's native integration.