Skip to content

Commit c15ef3c

Browse files
authored
Remove redundant definition of webhook form docs (#2561)
1 parent 1c62f9f commit c15ef3c

File tree

3 files changed

+0
-18
lines changed

3 files changed

+0
-18
lines changed

docs/docs/20-usage/10-intro.md

-6
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,6 @@ Webhooks are used to trigger pipeline executions. When you push code to your rep
1414
>
1515
> 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.
1616
17-
# Webhooks
18-
19-
When you activate your repository Woodpecker automatically add webhooks to your forge (e.g. GitHub). There is no manual configuration required.
20-
21-
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.
22-
2317
## Configuration
2418

2519
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.

docs/versioned_docs/version-0.15/20-usage/10-intro.md

-6
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,6 @@ Webhooks are used to trigger pipeline executions. When you push code to your rep
1414
>
1515
> 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.
1616
17-
# Webhooks
18-
19-
When you activate your repository Woodpecker automatically add webhooks to your version control system (e.g. GitHub). There is no manual configuration required.
20-
21-
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.
22-
2317
## Configuration
2418

2519
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.

docs/versioned_docs/version-1.0/20-usage/10-intro.md

-6
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,6 @@ Webhooks are used to trigger pipeline executions. When you push code to your rep
1414
>
1515
> 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.
1616
17-
# Webhooks
18-
19-
When you activate your repository Woodpecker automatically add webhooks to your forge (e.g. GitHub). There is no manual configuration required.
20-
21-
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.
22-
2317
## Configuration
2418

2519
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.

0 commit comments

Comments
 (0)