From c15ef3ca7613d905cc3e8c3b11c45eed8fb50250 Mon Sep 17 00:00:00 2001
From: Dhadve Yash <109629956+Exar04@users.noreply.github.com>
Date: Tue, 10 Oct 2023 19:45:49 +0530
Subject: [PATCH] Remove redundant definition of webhook form docs (#2561)

---
 docs/docs/20-usage/10-intro.md                        | 6 ------
 docs/versioned_docs/version-0.15/20-usage/10-intro.md | 6 ------
 docs/versioned_docs/version-1.0/20-usage/10-intro.md  | 6 ------
 3 files changed, 18 deletions(-)

diff --git a/docs/docs/20-usage/10-intro.md b/docs/docs/20-usage/10-intro.md
index 581260cec..fcefb8195 100644
--- a/docs/docs/20-usage/10-intro.md
+++ b/docs/docs/20-usage/10-intro.md
@@ -14,12 +14,6 @@ Webhooks are used to trigger pipeline executions. When you push code to your rep
 >
 > Note that manually creating webhooks yourself is not possible. This is because webhooks are signed using a per-repository secret key which is not exposed to end users.
 
-# Webhooks
-
-When you activate your repository Woodpecker automatically add webhooks to your forge (e.g. GitHub). There is no manual configuration required.
-
-Webhooks are used to trigger pipeline executions. When you push code to your repository, open a pull request, or create a tag, your forge will automatically send a webhook to Woodpecker which will in turn trigger pipeline execution.
-
 ## Configuration
 
 To configure your pipeline you must create a `.woodpecker.yml` file in the root of your repository. The `.woodpecker.yml` file is used to define your pipeline steps.
diff --git a/docs/versioned_docs/version-0.15/20-usage/10-intro.md b/docs/versioned_docs/version-0.15/20-usage/10-intro.md
index a227805c0..2673c7518 100644
--- a/docs/versioned_docs/version-0.15/20-usage/10-intro.md
+++ b/docs/versioned_docs/version-0.15/20-usage/10-intro.md
@@ -14,12 +14,6 @@ Webhooks are used to trigger pipeline executions. When you push code to your rep
 >
 > Note that manually creating webhooks yourself is not possible. This is because webhooks are signed using a per-repository secret key which is not exposed to end users.
 
-# Webhooks
-
-When you activate your repository Woodpecker automatically add webhooks to your version control system (e.g. GitHub). There is no manual configuration required.
-
-Webhooks are used to trigger pipeline executions. When you push code to your repository, open a pull request, or create a tag, your version control system will automatically send a webhook to Woodpecker which will in turn trigger pipeline execution.
-
 ## Configuration
 
 To configure your pipeline you should place a `.woodpecker.yml` file in the root of your repository. The .woodpecker.yml file is used to define your pipeline steps. It is a superset of the widely used docker-compose file format.
diff --git a/docs/versioned_docs/version-1.0/20-usage/10-intro.md b/docs/versioned_docs/version-1.0/20-usage/10-intro.md
index 581260cec..fcefb8195 100644
--- a/docs/versioned_docs/version-1.0/20-usage/10-intro.md
+++ b/docs/versioned_docs/version-1.0/20-usage/10-intro.md
@@ -14,12 +14,6 @@ Webhooks are used to trigger pipeline executions. When you push code to your rep
 >
 > Note that manually creating webhooks yourself is not possible. This is because webhooks are signed using a per-repository secret key which is not exposed to end users.
 
-# Webhooks
-
-When you activate your repository Woodpecker automatically add webhooks to your forge (e.g. GitHub). There is no manual configuration required.
-
-Webhooks are used to trigger pipeline executions. When you push code to your repository, open a pull request, or create a tag, your forge will automatically send a webhook to Woodpecker which will in turn trigger pipeline execution.
-
 ## Configuration
 
 To configure your pipeline you must create a `.woodpecker.yml` file in the root of your repository. The `.woodpecker.yml` file is used to define your pipeline steps.