From 47c85dc1bc5c8f3a032c2d74b9abe99a95603136 Mon Sep 17 00:00:00 2001
From: Florian Heberl <49693964+floh96@users.noreply.github.com>
Date: Sat, 22 Jan 2022 15:16:49 +0100
Subject: [PATCH] Fix Gitlab link (#3532)

---
 docs/documentation/sitespeed.io/continuous-integration/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/documentation/sitespeed.io/continuous-integration/index.md b/docs/documentation/sitespeed.io/continuous-integration/index.md
index a3d56824a..72be4d7e3 100644
--- a/docs/documentation/sitespeed.io/continuous-integration/index.md
+++ b/docs/documentation/sitespeed.io/continuous-integration/index.md
@@ -145,7 +145,7 @@ workflows:
 You will notice that the last run is reading the performance budget file that exists in the git repo that was checked out. This will only work if you mount the checked out repo as a volume for sitespeed. This makes is really efficient and convenient to allow sitespeed to pick up configuration files and to output results to a location where one can post-process with other scripts.
 
 ## Gitlab CI
-Gitlab has prepared an easy way to test using sitespeed.io: [https://docs.gitlab.com/ee/ci/examples/browser_performance.html](https://docs.gitlab.com/ee/ci/examples/browser_performance.html). 
+Gitlab has prepared an easy way to test using sitespeed.io: [https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html](https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html). 
 
 ## Grunt plugin
 Checkout the [grunt plugin](https://github.com/sitespeedio/grunt-sitespeedio).