From 01aa72e83ef73596f09f33d3f80fefd843e76175 Mon Sep 17 00:00:00 2001
From: George Tsiolis <tsiolis.g@gmail.com>
Date: Tue, 10 Sep 2024 14:57:38 +0300
Subject: [PATCH] Remove deprecated configuration for prebuilds in Gitpod
 integration

Gitpod Prebuilds configuration via .gitpod.yml has been deprecated, see relevant changelog and relevant docs.
---
 .../user-guide/integrations/gitpod/index.md   | 23 +------------------
 1 file changed, 1 insertion(+), 22 deletions(-)

diff --git a/content/en/user-guide/integrations/gitpod/index.md b/content/en/user-guide/integrations/gitpod/index.md
index 3b1f0b05bf..7da3a2f904 100644
--- a/content/en/user-guide/integrations/gitpod/index.md
+++ b/content/en/user-guide/integrations/gitpod/index.md
@@ -60,28 +60,7 @@ ports:
     onOpen: ignore
 ```
 
-If you are using GitHub, you can also use the [Gitpod Prebuilds](https://www.gitpod.io/docs/prebuilds/) feature to automatically build your workspace.
-This will allow you to start your workspace faster and with all the dependencies already installed.
-Add the following to your `.gitpod.yml` file:
-
-```yaml
-github:
-  prebuilds:
-    # enable for the default branch
-    master: true
-    # enable for all branches in this repo
-    branches: true
-    # enable for pull requests coming from this repo
-    pullRequests: true
-    # enable for pull requests coming from forks
-    pullRequestsFromForks: true
-    # add a check to pull requests
-    addCheck: true
-    # add a "Review in Gitpod" button as a comment to pull requests
-    addComment: false
-    # add a "Review in Gitpod" button to the pull request's description
-    addBadge: true
-```
+Enabling [Gitpod Prebuilds](https://www.gitpod.io/docs/configure/repositories/prebuilds) can help save time by executing `init` tasks defined in the `.gitpod.yml` ahead of time. 
 
 After adding the configuration, you can start your development & testing by creating [your workspace in Gitpod](https://www.gitpod.io/docs/getting-started/#start-your-first-workspace).
 Upon creation, you will be able to see the LocalStack container running in the background (you can use `localstack status` to check the status of the container).