dbt-labs · lostmygithubaccount · Aug 2, 2022 · Jul 29, 2022 · Aug 2, 2022
@@ -54,7 +54,7 @@ Advisory:
 
 Method 1: Utilizing the Cypress GUI
 1. Install `node`: `brew install node`
-2. Clone this repo: `git clone [email protected]:fishtown-analytics/docs.getdbt.com.git`
+2. Clone this repo: `git clone [email protected]:dbt-labs/docs.getdbt.com.git`
 3. `cd` into the repo: `cd docs.getdbt.com`
 4. `cd` into the `website` subdirectory: `cd website`
 5. Install the required node packages: `npm install`
@@ -63,7 +63,7 @@ Method 1: Utilizing the Cypress GUI
 
 Method 2: Running the Cypress E2E tests headlessly
 1. Install `node`: `brew install node`
-2. Clone this repo: `git clone [email protected]:fishtown-analytics/docs.getdbt.com.git`
+2. Clone this repo: `git clone [email protected]:dbt-labs/docs.getdbt.com.git`
 3. `cd` into the repo: `cd docs.getdbt.com`
 4. `cd` into the `website` subdirectory: `cd website`
 5. Install the required node packages: `npm install`

@@ -8,7 +8,7 @@ dbt Core and almost all of its adapter plugins are open source software. As such
 
 To download form source, you would clone the repositories from GitHub, making a local copy, and then install the local version using `pip`.
 
-Downloading and building dbt Core will enable you to contribute to the project by fixing a bug or implementing a sought-after feature. For more details, read the [contributing guidelines](https://github.com/dbt-labs/dbt/blob/HEAD/CONTRIBUTING.md).
+Downloading and building dbt Core will enable you to contribute to the project by fixing a bug or implementing a sought-after feature. For more details, read the [contributing guidelines](https://github.com/dbt-labs/dbt-core/blob/HEAD/CONTRIBUTING.md).
 
 ### Installing dbt Core
 

@@ -33,7 +33,7 @@ During initial installation, the KOTS appliance can be directly downloaded from
 - `quay.io`: Some dependencies of Replicated are hosted as public images in the Quay.io registry.
 - `hub.docker.com`: Some dependencies of Replicated are hosted as public images in Docker Hub.
 
-Replicated maintains a list of Replicated-owned IPs for IP access restriction purposes at https://github.com/replicatedhq/ips/blob/master/ip_addresses.json.
+Replicated maintains a list of Replicated-owned IPs for IP access restriction purposes at https://github.com/replicatedhq/ips/blob/main/ip_addresses.json.
 
 #### dbt Cloud Appliance Installation and Upgrades
 
@@ -61,7 +61,7 @@ To install the dbt Cloud appliance or perform updates, some external connections
 
 ```
 
-Replicated maintains a list of Replicated-owned IPs for IP access restriction purposes at https://github.com/replicatedhq/ips/blob/master/ip_addresses.json.
+Replicated maintains a list of Replicated-owned IPs for IP access restriction purposes at https://github.com/replicatedhq/ips/blob/main/ip_addresses.json.
 
 #### Ongoing Access
 

@@ -5,7 +5,7 @@ sidebar_label: 'Unable to checkout or create branch'
 id: gitignore
 ---
 
-If you're finding yourself unable to revert changes, check out a branch or click commit - this is usually do to your project missing a [.gitignore](https://github.com/fishtown-analytics/dbt-starter-project/blob/master/.gitignore) file OR your gitignore file doesn't contain the necessary content inside the folder.
+If you're finding yourself unable to revert changes, check out a branch or click commit - this is usually do to your project missing a [.gitignore](https://github.com/dbt-labs/dbt-starter-project/blob/main/.gitignore) file OR your gitignore file doesn't contain the necessary content inside the folder.
 
 This is what causes that 'commit' git action button to display. No worries though - to fix this, you'll need to complete the following steps in order:
 

@@ -5,7 +5,7 @@ sidebar_label: 'Unable to checkout or create branch'
 id: gitignore
 ---
 
-If you're finding yourself unable to revert changes, check out a branch or click commit - this is usually do to your project missing a .[gitignore](https://github.com/fishtown-analytics/dbt-starter-project/blob/master/.gitignore) file OR your gitignore file doesn't contain the necessary content inside the folder. 
+If you're finding yourself unable to revert changes, check out a branch or click commit - this is usually do to your project missing a .[gitignore](https://github.com/dbt-labs/dbt-starter-project/blob/main/.gitignore) file OR your gitignore file doesn't contain the necessary content inside the folder. 
 
 This is what causes that 'commit' git action button to display. No worries though - to fix this, you'll need to complete the following steps in order:
 

@@ -201,7 +201,7 @@ After you have moved everything into CTEs, you'll want to write a `select * from
 
 This allows anyone after us to easily step through the CTEs when troubleshooting, rather than having to untangle nested queries.
 
-> For more background on CTEs, check out the [dbt Labs style guide](https://github.com/dbt-labs/corp/blob/master/dbt_style_guide.md#ctes).
+> For more background on CTEs, check out the [dbt Labs style guide](https://github.com/dbt-labs/corp/blob/main/dbt_style_guide.md#ctes).
 
 ## Port CTEs to individual data models
 Rather than keep our SQL code confined to one long SQL file, we'll now start splitting it into modular + reusable [dbt data models](https://docs.getdbt.com/docs/building-a-dbt-project/building-models).
@@ -237,7 +237,7 @@ Our final model accomplishes the result set we want, and it uses the components
 
 <WistiaVideo id="dymp75cwh6" />
 
-We'll want to audit our results using the dbt [audit_helper package](https://hub.getdbt.com/fishtown-analytics/audit_helper/latest/). 
+We'll want to audit our results using the dbt [audit_helper package](https://hub.getdbt.com/dbt-labs/audit_helper/latest/). 
 
 Under the hood, it generates comparison queries between our before and after states, so that we can compare our original query results to our refactored results to identify differences.
 

@@ -11,7 +11,7 @@ All dbt projects should be managed in version control. Git branches should be cr
 
 :::info Git guide
 
-We've codified our best practices in Git, in our [Git guide](https://github.com/dbt-labs/corp/blob/master/git-guide.md).
+We've codified our best practices in Git, in our [Git guide](https://github.com/dbt-labs/corp/blob/main/git-guide.md).
 
 :::
 
@@ -23,7 +23,7 @@ SQL styles, field naming conventions, and other rules for your dbt project shoul
 
 :::info Our style guide
 
-We've made our [style guide](https://github.com/dbt-labs/corp/blob/master/dbt_style_guide.md) public – these can act as a good starting point for your own style guide.
+We've made our [style guide](https://github.com/dbt-labs/corp/blob/main/dbt_style_guide.md) public – these can act as a good starting point for your own style guide.
 
 :::
 
@@ -81,7 +81,7 @@ dbt provides a framework to test assumptions about the results generated by a mo
 
 :::info Recommended tests
 
-Our [style guide](https://github.com/dbt-labs/corp/blob/master/dbt_style_guide.md) recommends that at a minimum, every model should have a <Term id="primary-key" /> that is tested to ensure it is unique, and not null.
+Our [style guide](https://github.com/dbt-labs/corp/blob/main/dbt_style_guide.md) recommends that at a minimum, every model should have a <Term id="primary-key" /> that is tested to ensure it is unique, and not null.
 
 :::
 

@@ -41,7 +41,7 @@ When working on your package, we often find it useful to install a local copy of
 ### Follow our best practices
 _Modeling packages only_
 
-Use our [dbt coding conventions](https://github.com/dbt-labs/corp/blob/master/dbt_style_guide.md), our article on [how we structure our dbt projects](https://discourse.getdbt.com/t/how-we-structure-our-dbt-projects/355), and our [best practices](best-practices) for all of our advice on how to build your dbt project.
+Use our [dbt coding conventions](https://github.com/dbt-labs/corp/blob/main/dbt_style_guide.md), our article on [how we structure our dbt projects](https://discourse.getdbt.com/t/how-we-structure-our-dbt-projects/355), and our [best practices](best-practices) for all of our advice on how to build your dbt project.
 
 This is where it comes in especially handy to have worked on your own dbt project previously.
 
@@ -50,7 +50,7 @@ _Modeling packages only_
 
 Not every user of your package is going to store their Mailchimp data in a schema named `mailchimp`. As such, you'll need to make the location of raw data configurable.
 
-We recommend using [sources](using-sources) and [variables](using-variables) to achieve this. Check out [this package](https://github.com/fivetran/dbt_facebook_ads_source/blob/master/models/src_facebook_ads.yml#L5-L6) for an example — notably, the README [includes instructions](https://github.com/fivetran/dbt_facebook_ads_source#configuration) on how to override the default schema from a `dbt_project.yml` file.
+We recommend using [sources](using-sources) and [variables](using-variables) to achieve this. Check out [this package](https://github.com/fivetran/dbt_facebook_ads_source/blob/main/models/src_facebook_ads.yml#L5-L6) for an example — notably, the README [includes instructions](https://github.com/fivetran/dbt_facebook_ads_source#configuration) on how to override the default schema from a `dbt_project.yml` file.
 
 ### Install upstream packages from hub.getdbt.com
 
@@ -75,7 +75,7 @@ Many SQL functions are specific to a particular database. For example, the funct
 If you wish to support multiple warehouses, we have a number of tricks up our sleeve:
 - We've written a number of macros that compile to valid SQL snippets on each of the original four adapters. Where possible, leverage these macros.
 - If you need to implement cross-database compatibility for one of your macros, use the [`adapter.dispatch` macro](dispatch) to achieve this. Check out the cross-database macros in dbt-utils for examples.
-- If you're working on a modeling package, you may notice that you need write different models for each warehouse (for example, if the EL tool you are working with stores data differently on each warehouse). In this case, you can write different versions of each model, and use the [`enabled` config](enabled), in combination with [`target.type`](/reference/dbt-jinja-functions/target) to enable the correct models — check out [this package](https://github.com/fivetran/dbt_facebook_ads_creative_history/blob/master/dbt_project.yml#L11-L16) as an example.
+- If you're working on a modeling package, you may notice that you need write different models for each warehouse (for example, if the EL tool you are working with stores data differently on each warehouse). In this case, you can write different versions of each model, and use the [`enabled` config](enabled), in combination with [`target.type`](/reference/dbt-jinja-functions/target) to enable the correct models — check out [this package](https://github.com/fivetran/dbt_facebook_ads_creative_history/blob/main/dbt_project.yml#L11-L16) as an example.
 
 
 If your package has only been written to work for one <Term id="data-warehouse" />, make sure you document this in your package README.
@@ -132,7 +132,7 @@ packages:
 
 5. Confirm that you can run `dbt run` and `dbt test` from your command line successfully.
 
-5. (Optional) Use a CI tool, like CircleCI or GitHub Actions, to automate running your dbt project when you open a new Pull Request. For inspiration, check out one of our [CircleCI configs](https://github.com/dbt-labs/snowplow/blob/master/.circleci/config.yml), which runs tests against our four main warehouses. Note: this is an advanced step — if you are going down this path, you may find it useful to say hi on [dbt Slack](https://community.getdbt.com/).
+5. (Optional) Use a CI tool, like CircleCI or GitHub Actions, to automate running your dbt project when you open a new Pull Request. For inspiration, check out one of our [CircleCI configs](https://github.com/dbt-labs/snowplow/blob/main/.circleci/config.yml), which runs tests against our four main warehouses. Note: this is an advanced step — if you are going down this path, you may find it useful to say hi on [dbt Slack](https://community.getdbt.com/).
 
 ## 5. Deploy the docs for your package
 _Optional_

@@ -11,7 +11,7 @@ dbt Core v0.21 has reached the end of critical support. No new patch versions wi
 
 - [Discourse](https://discourse.getdbt.com/t/3077)
 - [Release notes](https://github.com/dbt-labs/dbt-core/releases/tag/v0.21.0)
-- [Full changelog](https://github.com/fishtown-analytics/dbt/blob/0.21.latest/CHANGELOG.md)
+- [Full changelog](https://github.com/dbt-labs/dbt-core/blob/0.21.latest/CHANGELOG.md)
 
 ## Breaking changes
 

@@ -11,7 +11,7 @@ dbt Core v0.20 has reached the end of critical support. No new patch versions wi
 
 - [Discourse](https://discourse.getdbt.com/t/2621)
 - [Release notes](https://github.com/dbt-labs/dbt-core/releases/tag/v0.20.0)
-- [Full changelog](https://github.com/fishtown-analytics/dbt/blob/0.20.latest/CHANGELOG.md)
+- [Full changelog](https://github.com/dbt-labs/dbt-core/blob/0.20.latest/CHANGELOG.md)
 
 ## Breaking changes
 

@@ -7,7 +7,7 @@ title: "Upgrading to 0.19.0"
 
 - [Discourse](https://discourse.getdbt.com/t/1951)
 - [Release notes](https://github.com/dbt-labs/dbt-core/releases/tag/v0.19.0)
-- [Full changelog](https://github.com/fishtown-analytics/dbt/blob/0.19.latest/CHANGELOG.md)
+- [Full changelog](https://github.com/dbt-labs/dbt-core/blob/0.19.latest/CHANGELOG.md)
 
 ## Breaking changes
 

@@ -83,7 +83,7 @@ Below that macro, I've defined three possible implementations of the `concat` ma
 
 ### A more complex example
 
-I found an existing implementation of the `concat` macro in the dbt-utils package. However, I want to override its implementation of the `concat` macro on Redshift in particular. In all other cases—including the default implementation—I'm perfectly happy falling back to the implementations defined in [`dbt_utils.concat`](https://github.com/dbt-labs/dbt-utils/blob/master/macros/cross_db_utils/concat.sql).
+I found an existing implementation of the `concat` macro in the dbt-utils package. However, I want to override its implementation of the `concat` macro on Redshift in particular. In all other cases—including the default implementation—I'm perfectly happy falling back to the implementations defined in [`dbt_utils.concat`](https://github.com/dbt-labs/dbt-utils/blob/main/macros/cross_db_utils/concat.sql).
 
 <File name='macros/concat.sql'>
 

@@ -9,7 +9,7 @@ title: "Defer"
 
 </Changelog>
 
-**N.B.** Deferral is a powerful, complex feature that enables compelling workflows. We reserve the right to change the name and syntax in a future version of dbt to make the behavior clearer and more intuitive. For details, see [dbt#2968](https://github.com/fishtown-analytics/dbt/issues/2968).
+**N.B.** Deferral is a powerful, complex feature that enables compelling workflows. We reserve the right to change the name and syntax in a future version of dbt to make the behavior clearer and more intuitive. For details, see [dbt#2968](https://github.com/dbt-labs/dbt-core/issues/2968).
 
 Defer is a powerful feature that makes it possible to run a subset of models or tests in a [sandbox environment](managing-environments), without having to first build their upstream parents. This can save time and computational resources when you want to test a small number of models in a large project.
 

@@ -56,7 +56,7 @@ If you ever get into a bad state, you can disable partial parsing and trigger a
 
 ## Static parser
 
-At parse time, dbt needs to extract the contents of `ref()`, `source()`, and `config()` from all models in the project. Traditionally, dbt has extracted those values by rendering the Jinja in every model file, which can be slow. In v0.20, we introduced a new way to statically analyze model files, leveraging [`tree-sitter`](https://github.com/tree-sitter/tree-sitter), which we're calling an "experimental parser". You can see the code for an initial Jinja2 grammar [here](https://github.com/fishtown-analytics/tree-sitter-jinja2).
+At parse time, dbt needs to extract the contents of `ref()`, `source()`, and `config()` from all models in the project. Traditionally, dbt has extracted those values by rendering the Jinja in every model file, which can be slow. In v0.20, we introduced a new way to statically analyze model files, leveraging [`tree-sitter`](https://github.com/tree-sitter/tree-sitter), which we're calling an "experimental parser". You can see the code for an initial Jinja2 grammar [here](https://github.com/dbt-labs/tree-sitter-jinja2).
 
 Starting in v1.0, the experimental parser is **on** by default. We believe it can offer *some* speedup to 95% of projects. You may optionally turn it off using the [`STATIC_PARSER` global config](global-configs#static-parser).
 

@@ -148,7 +148,7 @@ If you are disabling models because they are no longer being used, but you want
 
 ## Examples
 ### Disable a model in a package in order to use your own version of the model.
-This could be useful if you want to change the logic of a model in a package. For example, if you need to change the logic in the `segment_web_page_views` from the `segment` package ([original model](https://github.com/dbt-labs/segment/blob/master/models/base/segment_web_page_views.sql)):
+This could be useful if you want to change the logic of a model in a package. For example, if you need to change the logic in the `segment_web_page_views` from the `segment` package ([original model](https://github.com/dbt-labs/segment/blob/main/models/base/segment_web_page_views.sql)):
 1. Add a model named `segment_web_page_views` the same name to your own project.
 2. To avoid a compilation error due to duplicate models, disable the segment package's version of the model like so:
 

@@ -18,7 +18,7 @@ Optionally set a test to always or never store its failures in the database.
 `store_failures` config will take precedence over the presence or absence of the `--store-failures` flag.
 - If the `store_failures` config is `none` or omitted, the resource will use the value of the `--store-failures` flag.
 
-This logic is encoded in the [`should_store_failures()`](https://github.com/fishtown-analytics/dbt/blob/98c015b7754779793e44e056905614296c6e4527/core/dbt/include/global_project/macros/materializations/helpers.sql#L77) macro.
+This logic is encoded in the [`should_store_failures()`](https://github.com/dbt-labs/dbt-core/blob/98c015b7754779793e44e056905614296c6e4527/core/dbt/include/global_project/macros/materializations/helpers.sql#L77) macro.
 
 <Tabs
   defaultValue="specific"

@@ -357,7 +357,7 @@ version: 2
 
 models:
   - name: customers
-    description: "!\[dbt Logo](https://raw.githubusercontent.com/dbt-labs/dbt/develop/etc/dbt-logo.svg)"
+    description: "!\[dbt Logo](https://github.com/dbt-labs/dbt-core/blob/main/etc/dbt-core.svg)"
 
     columns:
       - name: customer_id

@@ -28,7 +28,7 @@ pip install dbt-ibmdb2
 This is an experimental plugin:
 - We have not tested it extensively
 - Tested with [dbt-adapter-tests](https://pypi.org/project/pytest-dbt-adapter/) and DB2 LUW on Mac OS+RHEL8
-- Compatibility with other [dbt packages](https://hub.getdbt.com/) (like [dbt_utils](https://hub.getdbt.com/fishtown-analytics/dbt_utils/latest/)) is only partially tested
+- Compatibility with other [dbt packages](https://hub.getdbt.com/) (like [dbt_utils](https://hub.getdbt.com/dbt-labs/dbt_utils/latest/)) is only partially tested
 
 ## Connecting to IBM DB2 with dbt-ibmdb2