Merge branch 'current' into fix/python-models-dataproc-serverless

.github/pull_request_template.md

@@ -1,23 +1,22 @@
 ## What are you changing in this pull request and why?
-<!---
-Describe your changes and why you're making them. If related to an open 
-issue or a pull request on dbt Core, then link to them here! 
+<!--
+Describe your changes and why you're making them. If related to an open issue or a pull request on dbt Core or another repository, then link to them here! 
 
 To learn more about the writing conventions used in the dbt Labs docs, see the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md).
 -->
 
 ## Checklist
+- [ ] I have reviewed the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines.
+- [ ] The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and/or [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content) guidelines.
+- [ ] I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
 <!--
-Uncomment when publishing docs for a prerelease version of dbt:
-- [ ] Add versioning components, as described in [Versioning Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
+PRE-RELEASE VERSION OF dbt (if so, uncomment):
 - [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
 -->
-- [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines.
-- [ ] For [docs versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning), review how to [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
-- [ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
-
-Adding or removing pages (delete if not applicable):
+<!-- 
+ADDING OR REMOVING PAGES (if so, uncomment):
 - [ ] Add/remove page in `website/sidebars.js`
 - [ ] Provide a unique filename for new pages
 - [ ] Add an entry for deleted pages in `website/vercel.json`
 - [ ] Run link testing locally with `npm run build` to update the links that point to deleted pages
+-->

contributing/single-sourcing-content.md

@@ -132,94 +132,6 @@ $ dbt test --models [...] --defer --state path/to/artifacts
 </VersionBlock>
 ```
 
-## Using global variables
-
----
-
-Global variables can be configured for use throughout the docs.
-
-Using a global variable requires two steps:
-
-1. Set the variable in the `website/dbt-global-variables.js` file.
-2. Use the **Var** component to add the global variable to a page.
-
-```jsx
-// The dbtCore property is the identifier for the variable,
-// while the name property is the value shown on the page.
-
-exports.dbtVariables = {
-  dbtCore: {
-    name: "dbt Core"
-  }
-}
-```
-
-```markdown
-// <Var name="dbtCore" /> is converted to dbt Core
-
-You can install <Var name="dbtCore" /> on the command line by using one of these recommended methods:
-```
-
-### Versioning global variables
-
-It is possible to version global variables as well. This creates the ability to show different variations of a string based off the current version a visitor has selected.
-
-To extend our `dbt-global-variables.js` file above, we can add a new variable: *note - these versions are not accurate and only shown for this example.*
-
-```jsx
-// A new variable called dbtCloud is added below
-// This variable includes a versions array
-// "Sinter" will replace "dbt Cloud" for versions 0.21 or lower
-
-exports.dbtVariables = {
-  dbtCore: {
-    name: "dbt Core"
-  },
-	dbtCloud: {
-		name: "dbt Cloud",
-		versions: [
-      {
-        "name": "Sinter",
-        "version": "0.21"
-      }
-    ]
-	}
-}
-```
-
-```markdown
-You can get started with <Var name="dbtCloud" /> by [Signing up](https://www.getdbt.com/signup/).
-```
-
-In the above example, the **dbtCloud** property has a default name of “dbt Cloud”. The naming for variables cascade down, meaning “dbt Cloud” will show for all versions, until version **0.21** or lower is selected. At that point “Sinter” will replace “dbt Cloud”.
-
-### Global variables properties
-
-**name** (required): Expects the identifier for a global variable.
-
-### Global variables example
-
-The global `<Var />` component can be used inline, for example:
-
-```markdown
-This piece of markdown content explains why <Var name="dbt" /> is awesome.
-```
-
-However, a Var component cannot start a new line of content. Fortunately, a workaround exists to use the Var component at the beginning of a line of content.
-
-To use the component at the beginning of a sentence, add a non-breaking space character before the component:
-
-```markdown
-// When starting a new line with a global variable,
-// a non-breaking space is required
-
-// Works
-&nbsp;<Var name="dbt" /> is awesome!
-
-// Does not work
-<Var name="dbt" /> is awesome!
-```
-
 ## Reusing content
 
 To reuse content on different pages, you can use some techniques like partial files or snippets. Partial files, a built-in Docusaurus feature, is the recommended method over snippets.

website/blog/2022-04-14-add-ci-cd-to-bitbucket.md

@@ -1,5 +1,5 @@
 ---
-title: "Slim CI/CD with Bitbucket Pipelines"
+title: "Slim CI/CD with Bitbucket Pipelines for dbt Core"
 description: "How to set up slim CI/CD outside of dbt Cloud"
 slug: slim-ci-cd-with-bitbucket-pipelines
 
@@ -10,8 +10,15 @@ hide_table_of_contents: false
 
 date: 2022-05-06
 is_featured: true
+keywords:
+  - dbt core pipeline, slim ci pipeline, slim cd pipeline, bitbucket
 ---
 
+
+:::info Set up CI/CD with dbt Cloud
+This blog is specifically tailored for dbt Core users. If you're using dbt Cloud and your Git provider doesn't have a native dbt Cloud integration (like BitBucket), follow the [Customizing CI/CD with custom pipelines guide](/guides/custom-cicd-pipelines?step=3) to set up CI/CD.
+:::
+
 Continuous Integration (CI) sets the system up to test everyone’s pull request before merging. Continuous Deployment (CD) deploys each approved change to production. “Slim CI” refers to running/testing only the changed code, [thereby saving compute](https://discourse.getdbt.com/t/how-we-sped-up-our-ci-runs-by-10x-using-slim-ci/2603). In summary, CI/CD automates dbt pipeline testing and deployment.
 
 [dbt Cloud](https://www.getdbt.com/), a much beloved method of dbt deployment, [supports GitHub- and Gitlab-based CI/CD](https://blog.getdbt.com/adopting-ci-cd-with-dbt-cloud/) out of the box. It doesn’t support Bitbucket, AWS CodeCommit/CodeDeploy, or any number of other services, but you need not give up hope even if you are tethered to an unsupported platform.