Changing syntax (#6281)

dbt-labs · Oct 14, 2024 · 64f06ab · 64f06ab
2 parents 245013c + 70498c2
commit 64f06ab
Showing 1 changed file with 13 additions and 13 deletions.
diff --git a/website/docs/docs/build/environment-variables.md b/website/docs/docs/build/environment-variables.md
@@ -101,7 +101,7 @@ dbt Cloud has a number of pre-defined variables built in. Variables are set auto
 
 The following environment variable is set automatically for the dbt Cloud IDE:
 
-- `DBT_CLOUD_GIT_BRANCH`: Provides the development Git branch name in the [dbt Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud).
+- `DBT_CLOUD_GIT_BRANCH` &mdash; Provides the development Git branch name in the [dbt Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud).
   - Available in dbt v 1.6 and later.
   - The variable changes when the branch is changed.
   - Doesn't require restarting the IDE after a branch change.
@@ -113,26 +113,26 @@ Use case &mdash; This is useful in cases where you want to dynamically use the G
 
 The following environment variables are set automatically: 
 
-- `DBT_ENV`: This key is reserved for the dbt Cloud application and will always resolve to 'prod'. For deployment runs only.
-- `DBT_CLOUD_ENVIRONMENT_NAME`: The name of the dbt Cloud environment in which `dbt` is running. 
-- `DBT_CLOUD_ENVIRONMENT_TYPE`: The type of dbt Cloud environment in which `dbt` is running. The valid values are `development` or `deployment`.
+- `DBT_ENV` &mdash; This key is reserved for the dbt Cloud application and will always resolve to 'prod'. For deployment runs only.
+- `DBT_CLOUD_ENVIRONMENT_NAME` &mdash; The name of the dbt Cloud environment in which `dbt` is running. 
+- `DBT_CLOUD_ENVIRONMENT_TYPE` &mdash; The type of dbt Cloud environment in which `dbt` is running. The valid values are `development` or `deployment`.
 
 #### Run details
 
-- `DBT_CLOUD_PROJECT_ID`: The ID of the dbt Cloud Project for this run
-- `DBT_CLOUD_JOB_ID`: The ID of the dbt Cloud Job for this run
-- `DBT_CLOUD_RUN_ID`: The ID of this particular run
-- `DBT_CLOUD_RUN_REASON_CATEGORY`: The "category" of the trigger for this run (one of: `scheduled`, `github_pull_request`, `gitlab_merge_request`, `azure_pull_request`, `other`)
-- `DBT_CLOUD_RUN_REASON`: The specific trigger for this run (eg. `Scheduled`, `Kicked off by <email>`, or custom via `API`)
-- `DBT_CLOUD_ENVIRONMENT_ID`: The ID of the environment for this run
-- `DBT_CLOUD_ACCOUNT_ID`: The ID of the dbt Cloud account for this run
+- `DBT_CLOUD_PROJECT_ID` &mdash; The ID of the dbt Cloud Project for this run
+- `DBT_CLOUD_JOB_ID` &mdash; The ID of the dbt Cloud Job for this run
+- `DBT_CLOUD_RUN_ID` &mdash; The ID of this particular run
+- `DBT_CLOUD_RUN_REASON_CATEGORY` &mdash; The "category" of the trigger for this run (one of: `scheduled`, `github_pull_request`, `gitlab_merge_request`, `azure_pull_request`, `other`)
+- `DBT_CLOUD_RUN_REASON` &mdash; The specific trigger for this run (eg. `Scheduled`, `Kicked off by <email>`, or custom via `API`)
+- `DBT_CLOUD_ENVIRONMENT_ID` &mdash; The ID of the environment for this run
+- `DBT_CLOUD_ACCOUNT_ID` &mdash; The ID of the dbt Cloud account for this run
 
 #### Git details
 
 _The following variables are currently only available for GitHub, GitLab, and Azure DevOps PR builds triggered via a webhook_
 
-- `DBT_CLOUD_PR_ID`: The Pull Request ID in the connected version control system
-- `DBT_CLOUD_GIT_SHA`: The git commit SHA which is being run for this Pull Request build
+- `DBT_CLOUD_PR_ID` &mdash; The Pull Request ID in the connected version control system
+- `DBT_CLOUD_GIT_SHA` &mdash; The git commit SHA which is being run for this Pull Request build
 
 
 ### Example usage