Merge branch 'current' into dbt-init-profile

.github/ISSUE_TEMPLATE/a-improve-docs.yml

@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        * You can ask questions or submit ideas for the dbt docs in [Discussions](https://github.com/dbt-labs/docs.getdbt.com/discussions)
+        * You can ask questions or submit ideas for the dbt docs in [Issues](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose)
         * Before you file an issue read the [Contributing guide](https://github.com/dbt-labs/docs.getdbt.com#contributing).
         * Check to make sure someone hasn't already opened a similar [issue](https://github.com/dbt-labs/docs.getdbt.com/issues).
 

.github/ISSUE_TEMPLATE/contribute-to-developer-blog.yml

@@ -1,4 +1,4 @@
-name: Contribute to the dbt Developer Blog
+name: Propose a dbt Developer Blog idea
 description: >
   For proposing a new post on the dbt Developer Blog.
 labels: ["content","developer blog"]

.github/ISSUE_TEMPLATE/improve-the-site.yml

@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        * You can ask questions or submit ideas for the dbt docs in [Discussions](https://github.com/dbt-labs/docs.getdbt.com/discussions)
+        * You can ask questions or submit ideas for the dbt docs in [Issues](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose)
         * Before you file an issue read the [Contributing guide](https://github.com/dbt-labs/docs.getdbt.com#contributing).
         * Check to make sure someone hasn't already opened a similar [issue](https://github.com/dbt-labs/docs.getdbt.com/issues).
 

.github/workflows/label.yml

@@ -2,37 +2,45 @@ name: Add/Remove Labels
 
 on:
   pull_request_target:
-    types: [ opened, closed ]
+    types: [opened]
 
 jobs:
   add_new_contributor_label:
     if: github.event.action == 'opened'
-    permissions:
-      contents: read
-      pull-requests: write
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/github-script@v6
-        with:
-          script: |
-            const creator = context.payload.sender.login
+    - name: Add new contributor label
+      uses: actions/github-script@v6
+      with:
+        github-token: ${{ secrets.DOCS_SECRET }}
+        script: |
+            const creator = context.payload.sender.login;
             const opts = github.rest.issues.listForRepo.endpoint.merge({
               ...context.issue,
               creator,
-              state: 'all'
-            })
-            const issues = await github.paginate(opts)
+              state: 'all',
+            });
+            
+            const issues = await github.paginate(opts);
+            
+            let isAlreadyContributor = false;
+            
             for (const issue of issues) {
               if (issue.number === context.issue.number) {
-                continue
+                continue;
               }
-              if (issue.pull_request) {
-                return // creator is already a contributor
+              if (issue.pull_request && issue.user.login === creator) {
+                isAlreadyContributor = true;
+                break;
               }
             }
-            await github.rest.issues.addLabels({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              labels: ['new contributor']
-            })
+            
+            if (!isAlreadyContributor) {
+              console.log('Adding label: new contributor');
+              await github.rest.issues.addLabels({
+                issue_number: context.issue.number,
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                labels: ['new contributor'],
+              });
+            } 

.github/workflows/labeler.yml

@@ -5,8 +5,8 @@
 
 name: "Pull Request Labeler"
 on:
-- pull_request_target
-
+  pull_request_target:
+    types: [opened]
 jobs:
   triage:
     permissions:

README.md

@@ -17,7 +17,7 @@ Creating an inclusive and equitable environment for our documents is more import
 We welcome contributions from community members to this repo:
 - **Fixes**: When you notice an error, you can use the `Edit this page` button at the bottom of each page to suggest a change.
 - **New documentation**: If you contributed code in [dbt-core](https://github.com/dbt-labs/dbt-core), we encourage you to also write the docs here! Please reach out in the dbt community if you need help finding a place for these docs.
-- **Major rewrites**: You can [file an issue](https://github.com/dbt-labs/docs.getdbt.com/issues/new?assignees=&labels=content%2Cimprovement&template=improve-docs.yml) or [start a discussion](https://github.com/dbt-labs/docs.getdbt.com/discussions) to propose ideas for a content area that requires attention.
+- **Major rewrites**: You can [file an issue](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose) to propose ideas for a content area that requires attention.
 
 You can use components documented in the [docusaurus library](https://v2.docusaurus.io/docs/markdown-features/).
 

website/blog/2020-07-01-how-to-create-near-real-time-models-with-just-dbt-sql.md

@@ -13,6 +13,13 @@ date: 2020-07-01
 is_featured: false
 ---
 
+:::caution More up-to-date information available
+
+Since this blog post was first published, many data platforms have added support for [materialized views](/blog/announcing-materialized-views), which are a superior way to achieve the goals outlined here. We recommend them over the below approach. 
+
+
+:::
+
 Before I dive into how to create this, I have to say this. **You probably don’t need this**. I, along with my other Fishtown colleagues, have spent countless hours working with clients that ask for near-real-time streaming data. However, when we start digging into the project, it is often realized that the use case is not there. There are a variety of reasons why near real-time streaming is not a good fit. Two key ones are:
 
 1.  The source data isn’t updating frequently enough.

website/blog/ctas.yml

@@ -10,3 +10,8 @@
   subheader: Check out guides on getting your warehouse set up and connected to dbt Cloud.
   button_text: Learn more
   url: https://docs.getdbt.com/quickstarts
+- name: coalesce_2023_signup
+  header: Join data practitioners worldwide at Coalesce 2023
+  subheader: Kicking off on October 16th, both online and in-person (Sydney, London, and San Diego)
+  button_text: Register now
+  url: https://coalesce.getdbt.com/?utm_medium=internal&utm_source=docs&utm_campaign=q3-2024_coalesce-2023_aw&utm_content=coalesce____&utm_term=all___

website/blog/metadata.yml

@@ -2,7 +2,7 @@
 featured_image: ""
 
 # This CTA lives in right sidebar on blog index
-featured_cta: "staging"
+featured_cta: "coalesce_2023_signup"
 
 # Show or hide hero title, description, cta from blog index
 show_title: true

website/dbt-versions.js

@@ -24,13 +24,61 @@ exports.versions = [
     version: "1.2",
     EOLDate: "2023-07-26",
   },
-  {
-    version: "1.1",
-    EOLDate: "2023-04-28",
-  },
 ]
 
 exports.versionedPages = [
+  {
+    "page": "docs/build/build-metrics-intro",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/sl-getting-started",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/about-metricflow",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/join-logic",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/validation",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/semantic-models",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/group-by",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/entities",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/metrics-overview",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/cumulative",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/derived",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/measure-proxy",
+    "firstVersion": "1.6",
+  },
+  {
+    "page": "docs/build/ratio",
+    "firstVersion": "1.6",
+  },
   {
     "page": "reference/commands/clone",
     "firstVersion": "1.6",
@@ -122,70 +170,6 @@ exports.versionedPages = [
   {
     "page": "reference/resource-configs/grants",
     "firstVersion": "1.2",
-  },
-  {
-    "page": "docs/contributing/testing-a-new-adapter",
-    "firstVersion": "1.1",
-  },
-  {
-    "page": "reference/dbt-jinja-functions/selected_resources",
-    "firstVersion": "1.1",
-  },
-  {
-    "page": "reference/dbt-jinja-functions/print",
-    "firstVersion": "1.1",
-  },
-  {
-    "page": "docs/build/build-metrics-intro",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/sl-getting-started",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/about-metricflow",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/join-logic",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/validation",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/semantic-models",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/group-by",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/entities",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/metrics-overview",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/cumulative",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/derived",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/measure-proxy",
-    "firstVersion": "1.6",
-  },
-  {
-    "page": "docs/build/ratio",
-    "firstVersion": "1.6",
   }
 ]
 

website/docs/community/resources/jobs-terms-and-conditions.md

@@ -0,0 +1,16 @@
+---
+title: "dbt Labs Community #jobs Channels Terms and Conditions"
+id: "jobs-terms-and-conditions"
+description: "Before posting a job in the dbt Community or submitting an application, review these terms and conditions."
+---
+
+I agree to abide by the [dbt Community Code of Conduct](community/resources/code-of-conduct) and all laws applicable to me in my use of the dbt Community's #jobs channels. I further agree:
+
+- dbt Labs is not responsible for not does it warrant or guarantee the validity, accuracy, completeness, legality, or reliability of any functionality of any #jobs channel, any posting's content, or any application and/or solicitation of any kind of employment.
+- dbt Labs does not review and approve job-related content.
+- dbt Labs disclaims liability of any kind whatsoever for any type of damage that occurs while using the community Slack for job-related reasons, and I waive any type of claim (including actual, special or consequential damages) to the maximum extent permitted by law.
+- Without limitation, dbt Labs disclaims liability for quality, performance, merchantability, and fitness for a particular purpose, express or implied, that may arise out of my use of the community Slack for job-related content, my reliance on such information, and/or my provision/receipt of job-related information.
+- I understand that no internet-based site is without risk, and my use is at my own risk.
+- My use of any job-posting template (or other forum for providing job-related information) confirms my consent to provide the data posted, confirms that I have permission to post such data, and is subject to the terms of the [dbt Labs privacy policy](https://www.getdbt.com/cloud/privacy-policy).
+
+For further information, please contact [[email protected]](mailto:[email protected]).

website/docs/community/resources/oss-expectations.md

@@ -4,7 +4,7 @@ title: "Expectations for OSS contributors"
 
 Whether it's a dbt package, a plugin, `dbt-core`, or this very documentation site, contributing to the open source code that supports the dbt ecosystem is a great way to level yourself up as a developer, and to give back to the community. The goal of this page is to help you understand what to expect when contributing to dbt open source software (OSS). While we can only speak for our own experience as open source maintainers, many of these guidelines apply when contributing to other open source projects, too.
 
-Have you seen things in other OSS projects that you quite like, and think we could learn from? [Open a discussion on the Developer Hub](https://github.com/dbt-labs/docs.getdbt.com/discussions/new), or start a conversation in the dbt Community Slack (for example: `#community-strategy`, `#dbt-core-development`, `#package-ecosystem`, `#adapter-ecosystem`). We always appreciate hearing from you!
+Have you seen things in other OSS projects that you quite like, and think we could learn from? [Open a discussion on the dbt Community Forum](https://discourse.getdbt.com), or start a conversation in the dbt Community Slack (for example: `#community-strategy`, `#dbt-core-development`, `#package-ecosystem`, `#adapter-ecosystem`). We always appreciate hearing from you!
 
 ## Principles
 
@@ -51,7 +51,7 @@ An issue could be a bug you’ve identified while using the product or reading t
 
 ### Best practices for issues
 
-- Issues are **not** for support / troubleshooting / debugging help. Please [open a discussion on the Developer Hub](https://github.com/dbt-labs/docs.getdbt.com/discussions/new), so other future users can find and read proposed solutions. If you need help formulating your question, you can post in the `#advice-dbt-help` channel in the [dbt Community Slack](https://www.getdbt.com/community/).
+- Issues are **not** for support / troubleshooting / debugging help. Please [open a discussion on the dbt Community Forum](https://discourse.getdbt.com), so other future users can find and read proposed solutions. If you need help formulating your question, you can post in the `#advice-dbt-help` channel in the [dbt Community Slack](https://www.getdbt.com/community/).
 - Always search existing issues first, to see if someone else had the same idea / found the same bug you did.
 - Many repositories offer templates for creating issues, such as when reporting a bug or requesting a new feature. If available, please select the relevant template and fill it out to the best of your ability. This will help other people understand your issue and respond.
 

website/docs/docs/build/custom-databases.md

@@ -54,8 +54,6 @@ select * from ...
 
 ### generate_database_name
 
-<Changelog>New in v0.16.0</Changelog>
-
 The database name generated for a model is controlled by a macro called `generate_database_name`. This macro can be overridden in a dbt project to change how dbt generates model database names. This macro works similarly to the [generate_schema_name](/docs/build/custom-schemas#advanced-custom-schema-configuration) macro.
 
 To override dbt's database name generation, create a macro named `generate_database_name` in your own dbt project. The `generate_database_name` macro accepts two arguments:

website/docs/docs/build/custom-schemas.md

@@ -180,13 +180,6 @@ The following context methods _are_ available in the `generate_schema_name` macr
 
 ### Which vars are available in generate_schema_name?
 
-<Changelog>
-
-Variable semantics have changed in dbt v0.17.0. See the [migration guide](/guides/migration/versions)
-for more information on these changes.
-
-</Changelog>
-
 Globally-scoped variables and variables defined on the command line with
 [--vars](/docs/build/project-variables) are accessible in the `generate_schema_name` context.
 

website/docs/docs/build/exposures.md

@@ -4,13 +4,6 @@ sidebar_label: "Exposures"
 id: "exposures"
 ---
 
-<Changelog>
-
-* **v0.18.1**: Exposures are new!
-* **v0.20.0**: Exposures support `tags` and `meta` properties
-
-</Changelog>
-
 Exposures make it possible to define and describe a downstream use of your dbt project, such as in a dashboard, application, or data science pipeline. By defining exposures, you can then:
 - run, test, and list resources that feed into your exposure
 - populate a dedicated page in the auto-generated [documentation](/docs/collaborate/documentation) site with context relevant to data consumers