From d379a4be9f5a9032be063257b56fd0ffb108c19f Mon Sep 17 00:00:00 2001
From: nataliefiann <120089939+nataliefiann@users.noreply.github.com>
Date: Fri, 10 Jan 2025 11:34:45 +0000
Subject: [PATCH] Update website/snippets/_git-providers-supporting-ci.md

Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
---
 website/snippets/_git-providers-supporting-ci.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/snippets/_git-providers-supporting-ci.md b/website/snippets/_git-providers-supporting-ci.md
index e0c0a9f4b2..34bd87db2f 100644
--- a/website/snippets/_git-providers-supporting-ci.md
+++ b/website/snippets/_git-providers-supporting-ci.md
@@ -2,7 +2,7 @@
 
 - If your git provider has a [native dbt Cloud integration](/docs/cloud/git/git-configuration-in-dbt-cloud), you can seamlessly set up [continuous integration (CI)](/docs/deploy/ci-jobs) jobs directly within dbt Cloud. 
 
-- For providers without native integration, you can still use the git clone method to import your git URL and leverage the [dbt Cloud Administrative API](/docs/dbt-cloud-apis/admin-cloud-api) to trigger a CI job to run.
+- For providers without native integration, you can still use the [Git clone method](/docs/cloud/git/import-a-project-by-git-url) to import your git URL and leverage the [dbt Cloud Administrative API](/docs/dbt-cloud-apis/admin-cloud-api) to trigger a CI job to run.
 
 The following table outlines the available integration options and their corresponding capabilities.