From 312058104ddc817026f86b7f02a64a3b0b501ac5 Mon Sep 17 00:00:00 2001
From: nataliefiann <120089939+nataliefiann@users.noreply.github.com>
Date: Fri, 20 Dec 2024 10:52:18 +0000
Subject: [PATCH] Update website/docs/docs/deploy/continuous-integration.md

Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
---
 website/docs/docs/deploy/continuous-integration.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/deploy/continuous-integration.md b/website/docs/docs/deploy/continuous-integration.md
index a808d98544f..cd585e5ab09 100644
--- a/website/docs/docs/deploy/continuous-integration.md
+++ b/website/docs/docs/deploy/continuous-integration.md
@@ -31,7 +31,7 @@ dbt Cloud deletes the temporary schema from your <Term id="data-warehouse" /> w
 
 If your git provider has a native dbt Cloud integration, you can set up continuous integration (CI) jobs within dbt Cloud.
 
-| **Git provider** | **Native dbt Cloud integration** |[**Automated CI job**](/docs/deploy/ci-jobs)|**Git import with URL**| **Information**|
+| **Git provider** | **Native dbt Cloud integration** |**Automated CI job** |**Git import with URL**| **Information**|
 | -----------------| ---------------------------------| -------------------------------------------|-----------------------|---------|
 |[Azure DevOps](/docs/cloud/git/setup-azure) <Lifecycle status="enterprise" />|  ✅|  ✅ |  ✅  | Organizations on the Team Plan can connect to Azure DeveOps via deploy key. Note, you won’t get the automated CI jobs but you can still develop.|
 |[GitHub](/docs/cloud/git/connect-github) <Lifecycle status="developer,team,enterprise" /> | ✅ | ✅ |  ✅         |