From f5bbcfc0a1ed1be18d675520ee281ef559b2b1fc Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 11:57:41 -0600 Subject: [PATCH 01/16] Add connection types section --- src/segment-app/extensions/git.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index 7a2f920a7f..eae8bd83d1 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -76,3 +76,21 @@ To manage Segment resources using Git and Terraform, follow these steps: For more information on using Terraform, visit [Terraform's documentation](https://developer.hashicorp.com/terraform/docs){:target="_blank"}. + +## Git Connections + +Git Connections enable Segment to sync data with your preferred Git repository through supported connection types. Segment supports several connection options connecting, including SSH and token-based authentication. + +> info "" +> Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. + +### Supported connection types + +Segment supports the following credential types for setting up a Git Connection: + +- **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. +- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. +- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, such as [CI checks](). + + + From 63965a4170646ce85420e539b38e88a238d43111 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:03:09 -0600 Subject: [PATCH 02/16] add reusing git connections section --- src/segment-app/extensions/git.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index eae8bd83d1..10d3c3c63e 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -92,5 +92,10 @@ Segment supports the following credential types for setting up a Git Connection: - **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. - **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, such as [CI checks](). +### Reusing Git Connections + +Segment lets you set up multiple Git Connections, allowing you to reuse credentials across both dbt and Git Sync. You can either use the same credential for multiple configurations or create separate Git Connections for each product and environment as needed. + +If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. From 4e0e5a0b761619b8f16ac8e55357fdd41adddeb6 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:04:49 -0600 Subject: [PATCH 03/16] Add Git Connections section to dbt page --- src/segment-app/extensions/dbt.md | 21 +++++++++++++++++++++ src/segment-app/extensions/git.md | 3 +-- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 547bcdcfc4..a39aee6efb 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -69,3 +69,24 @@ After you've successfully set up dbt with a warehouse and connected to your Git 6. Enter your **Model Name**, then click **Create Model**. To change a connected model, ensure that you've removed it from all active Reverse ETL syncs. + +## Git Connections + +Git Connections enable Segment to sync data with your preferred Git repository through supported connection types. Segment supports several connection options connecting, including SSH and token-based authentication. + +> info "" +> Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. + +### Supported connection types + +Segment supports the following credential types for setting up a Git Connection: + +- **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. +- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. +- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like [CI checks](). + +### Reusing Git Connections + +Segment lets you set up multiple Git Connections, allowing you to reuse credentials across both dbt and Git Sync. You can either use the same credential for multiple configurations or create separate Git Connections for each product and environment as needed. + +If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. \ No newline at end of file diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index 10d3c3c63e..93c2d212c5 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -90,7 +90,7 @@ Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. - **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. -- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, such as [CI checks](). +- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like CI checks. ### Reusing Git Connections @@ -98,4 +98,3 @@ Segment lets you set up multiple Git Connections, allowing you to reuse credenti If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. - From b7836ed4a91d0d6b4dd68859ee90ff2a82cab453 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:08:58 -0600 Subject: [PATCH 04/16] CI checks info --- src/segment-app/extensions/dbt.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index a39aee6efb..c82c265f31 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -89,4 +89,16 @@ Segment supports the following credential types for setting up a Git Connection: Segment lets you set up multiple Git Connections, allowing you to reuse credentials across both dbt and Git Sync. You can either use the same credential for multiple configurations or create separate Git Connections for each product and environment as needed. -If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. \ No newline at end of file +If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. + +## Setting Up CI checks + +> info "CI Check availability" +> CI Checks are available only with the GitHub App connection. + +CI checks in Segment help prevent breaking changes to active dbt models. Avoid changing dbt models currently in use with an active Reverse ETL sync, since changes could disrupt existing mappings and active syncs. + +When CI checks are enabled, Segment monitors model changes in your Git repository. If a model already linked to an active Reverse ETL sync gets modified, Segment automatically rejects the change to maintain data integrity. + +To enable CI Checks, authorize a GitHub App credential for your Git connection. Once connected, you can enable CI Checks in the dbt model sync configuration section. + From 61f05e26b11aeb4823cd7f01125e938325db913e Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:12:10 -0600 Subject: [PATCH 05/16] troubleshooting sections --- src/segment-app/extensions/dbt.md | 2 ++ src/segment-app/extensions/git.md | 1 + 2 files changed, 3 insertions(+) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index c82c265f31..4d1d2bc109 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -102,3 +102,5 @@ When CI checks are enabled, Segment monitors model changes in your Git repositor To enable CI Checks, authorize a GitHub App credential for your Git connection. Once connected, you can enable CI Checks in the dbt model sync configuration section. +## Troubleshooting dbt Extensions + diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index 93c2d212c5..e36ea3fd7c 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -98,3 +98,4 @@ Segment lets you set up multiple Git Connections, allowing you to reuse credenti If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. +## Troubleshooting Git Sync From 5c8bd727579525182bca44792f1421332fe68e74 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:19:46 -0600 Subject: [PATCH 06/16] add troubleshooting section --- src/segment-app/extensions/dbt.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 4d1d2bc109..712191e60b 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -83,7 +83,7 @@ Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. - **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. -- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like [CI checks](). +- **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like [CI checks](#setting-up-ci-checks). ### Reusing Git Connections @@ -104,3 +104,9 @@ To enable CI Checks, authorize a GitHub App credential for your Git connection. ## Troubleshooting dbt Extensions +The following table lists common dbt Extension errors, as well as their solutions: + +| Error | Error message | Solution | +| ----------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Failed sync | `Sync Failed: Incorrect dbt Project File Path: dbt project file not found` | Verify that the path to your `dbt_project.yml` file is relative to the repository root, excluding the root branch.
For example, use `project/dbt_project.yml` instead of `main/project/dbt_project.yml`. | +| Failed sync | `Sync Failed: remote: Write access to repository not granted` | Verify that the account associated with the token has a write role in the repository settings. Fine-grained tokens may require specific roles, depending on your Git provider. | \ No newline at end of file From 5bd65ed42269398163947c4124cc6e69cbac4313 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:24:35 -0600 Subject: [PATCH 07/16] git troubleshooting --- src/segment-app/extensions/git.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index e36ea3fd7c..b6b7dee43e 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -99,3 +99,11 @@ Segment lets you set up multiple Git Connections, allowing you to reuse credenti If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the necessary read and write permissions for both integrations. ## Troubleshooting Git Sync + +When setting up Git Sync, you may run into an access error when setting up Git Sync with the following message: `“Unable to create Git Sync due to Git connection issues. Please check your configuration and try again`. + +This error can occur if there are issues with your Git connection settings or permissions. To resolve the error, verify that: + +- Your credentials have write access to the Git repository, as Segment requires this to sync changes. +- Your repository is hosted by GitHub, GitLab, or Bitbucket (Segment doesn't support self-hosted repositories). +- Branch protections are disabled on the repository. From ca0bdc3cb3b561ad0d8a84df211b8c582c476357 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:28:31 -0600 Subject: [PATCH 08/16] final touches [netlify-build] --- src/segment-app/extensions/git.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index b6b7dee43e..bb3009dabf 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -23,7 +23,7 @@ The Git sync extension syncs the following resources from Segment to your Git re - [Sources](/docs/connections/sources/) and [Destinations](/docs/connections/destinations/) - [Warehouses](/docs/connections/storage/warehouses/) -- [Destination Filters and Mappings](/docs/connections/destinations/destination-filters/) +- [Destination Filters and Mappings](/docs/connections/destinations/destination-filters/) for Connections - [Tracking Plans](/docs/protocols/tracking-plan/create/) - [Functions](/docs/connections/functions/) - [Transformations](/docs/protocols/transform/) @@ -31,6 +31,13 @@ The Git sync extension syncs the following resources from Segment to your Git re - [Users](/docs/segment-app/iam/concepts/#team-members) and [User groups](/docs/segment-app/iam/concepts/#user-groups) - [Labels](/docs/segment-app/iam/labels/#where-can-i-create-labels) +The Git sync extension doesn't support the following resources: + +- [Spaces](/docs/segment-app/workspace-home/) +- [Audiences](/docs/engage/audiences/) and [Journeys](/docs/engage/journeys/) +- [Data Graph](/docs/unify/data-graph/) +- Mappings for [Linked Audiences](/docs/engage/audiences/linked-audiences/) + Reach out to [Segment support](https://app.segment.com/workspaces?contact=1){:target="blank"} to request support for additional Git Sync resources. After you set up the Git sync extension for the first time, Segment performs an initial sync that sends the current state of your Segment workspace to the Git repository you connected. Segment automatically tracks all following workspace updates. @@ -49,7 +56,7 @@ Using HCL makes it easier to document Segment's data model, especially for users Segment supports one-way synchronization from Segment to Git, but you can set up two-way synchronization using the Segment Terraform provider. -Terraform offers an open-source way to manage Segment resources through a Git repository as an alternative to a fully managed two-way sync. However, this method requires third-party tools like [Atlantis](https://www.runatlantis.io/){:target="_blank"} for CI integration, which Segment doesn’t officially support. +Terraform offers an open-source way to manage Segment resources through a Git repository as an alternative to a fully managed two-way sync. This method requires third-party tools like [Atlantis](https://www.runatlantis.io/){:target="_blank"} for CI integration. To manage Segment resources using Git and Terraform, follow these steps: From 06fa7ffe8bf2232ef5bbf2b5aac0a4f584620213 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:32:08 -0600 Subject: [PATCH 09/16] some more fixes --- src/segment-app/extensions/dbt.md | 2 +- src/segment-app/extensions/git.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 712191e60b..66edce2303 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -72,7 +72,7 @@ To change a connected model, ensure that you've removed it from all active Rever ## Git Connections -Git Connections enable Segment to sync data with your preferred Git repository through supported connection types. Segment supports several connection options connecting, including SSH and token-based authentication. +Git Connections enable Segment to sync data with your preferred Git repository through supported like SSH and token-based authentication. > info "" > Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index bb3009dabf..c522c303b6 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -86,7 +86,7 @@ For more information on using Terraform, visit [Terraform's documentation](https ## Git Connections -Git Connections enable Segment to sync data with your preferred Git repository through supported connection types. Segment supports several connection options connecting, including SSH and token-based authentication. +Git Connections enable Segment to sync data with your preferred Git repository through supported like SSH and token-based authentication. > info "" > Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. @@ -96,7 +96,7 @@ Git Connections enable Segment to sync data with your preferred Git repository t Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. -- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. +- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication.. - **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like CI checks. ### Reusing Git Connections From 7840eae47d4d813efc5873495ed26e1ef25e43db Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 7 Nov 2024 12:33:04 -0600 Subject: [PATCH 10/16] even more fixes --- src/segment-app/extensions/git.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index c522c303b6..9be4925088 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -107,7 +107,7 @@ If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the ## Troubleshooting Git Sync -When setting up Git Sync, you may run into an access error when setting up Git Sync with the following message: `“Unable to create Git Sync due to Git connection issues. Please check your configuration and try again`. +When setting up Git Sync, you may run into an access error with the following message: `“Unable to create Git Sync due to Git connection issues. Please check your configuration and try again`. This error can occur if there are issues with your Git connection settings or permissions. To resolve the error, verify that: From 8acc4c14a1ad2a6d1970e894d07cd7de17a2be3a Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:42:49 -0600 Subject: [PATCH 11/16] Update src/segment-app/extensions/git.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/git.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index 9be4925088..da1aa02735 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -89,7 +89,7 @@ For more information on using Terraform, visit [Terraform's documentation](https Git Connections enable Segment to sync data with your preferred Git repository through supported like SSH and token-based authentication. > info "" -> Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. +> Git Sync and the dbt integration operate independently. You don’t need to set up Git Sync to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. ### Supported connection types From 10328cd2cda5ec2c159f9e7be60fd66f1a099270 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:42:57 -0600 Subject: [PATCH 12/16] Update src/segment-app/extensions/dbt.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/dbt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 66edce2303..335ab21d58 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -94,7 +94,7 @@ If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the ## Setting Up CI checks > info "CI Check availability" -> CI Checks are available only with the GitHub App connection. +> CI checks are available only with the GitHub App connection. CI checks in Segment help prevent breaking changes to active dbt models. Avoid changing dbt models currently in use with an active Reverse ETL sync, since changes could disrupt existing mappings and active syncs. From 5196788ee755e59eede9bf875328e946bff76d98 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:43:08 -0600 Subject: [PATCH 13/16] Update src/segment-app/extensions/dbt.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/dbt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 335ab21d58..d2622e6779 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -93,7 +93,7 @@ If you plan to reuse a Git token across both dbt and Git Sync, ensure it has the ## Setting Up CI checks -> info "CI Check availability" +> info "CI check availability" > CI checks are available only with the GitHub App connection. CI checks in Segment help prevent breaking changes to active dbt models. Avoid changing dbt models currently in use with an active Reverse ETL sync, since changes could disrupt existing mappings and active syncs. From d64b6e8899d38b1f2e5e34a105c40860ecc97143 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:43:24 -0600 Subject: [PATCH 14/16] Update src/segment-app/extensions/dbt.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/dbt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index d2622e6779..6c885657aa 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -82,7 +82,7 @@ Git Connections enable Segment to sync data with your preferred Git repository t Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. -- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. +- **Git token**: Git tokens are supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication for added flexibility. - **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like [CI checks](#setting-up-ci-checks). ### Reusing Git Connections From 64c9119556a028ff9639d08cc5cb748a92720bb5 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:45:10 -0600 Subject: [PATCH 15/16] Update src/segment-app/extensions/dbt.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/segment-app/extensions/dbt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/dbt.md b/src/segment-app/extensions/dbt.md index 6c885657aa..2b811103de 100644 --- a/src/segment-app/extensions/dbt.md +++ b/src/segment-app/extensions/dbt.md @@ -75,7 +75,7 @@ To change a connected model, ensure that you've removed it from all active Rever Git Connections enable Segment to sync data with your preferred Git repository through supported like SSH and token-based authentication. > info "" -> Git Sync and the dbt integration operate independently. You don’t need Git Sync set up to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. +> Git Sync and the dbt integration operate independently. You don’t need to set up Git Sync to use dbt, and dbt Cloud can trigger its own syncs without relying on Git Sync. ### Supported connection types From e01c6dbcd008eaf4986e9c2625fd12cc861b0ac6 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 7 Nov 2024 12:49:31 -0600 Subject: [PATCH 16/16] token not Token smh --- src/segment-app/extensions/git.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/segment-app/extensions/git.md b/src/segment-app/extensions/git.md index da1aa02735..04b87ed6c9 100644 --- a/src/segment-app/extensions/git.md +++ b/src/segment-app/extensions/git.md @@ -96,7 +96,7 @@ Git Connections enable Segment to sync data with your preferred Git repository t Segment supports the following credential types for setting up a Git Connection: - **SSH**: Compatible with GitHub, GitLab, and Bitbucket, SSH provides a secure method for connecting to your repository. -- **Git Token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication.. +- **Git token**: Git tokens are also supported across GitHub, GitLab, and Bitbucket, enabling token-based authentication.. - **GitHub App**: For GitHub users, GitHub App integrations offer enhanced security and functionality. This method is exclusive to GitHub and supports additional features, like CI checks. ### Reusing Git Connections