Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

Commit 609c02a

Browse files
committed
Configuration documentation update
1 parent a6bdc75 commit 609c02a

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

configuration.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -41,19 +41,15 @@ Configure a Github project with a webhook with a format like this: https://<rece
4141

4242
You can test other events, but just validating that an issue.created event is generated in Kafka is enough to smoke test the receiver is set up properly.
4343

44-
#### Debugging
45-
You can re-run and debug the responses to webhook requests on Github, in the configuration for the webhook. This can be useful if things aren't coming through properly in the receiver.
46-
47-
## Github Verification
44+
## Gitlab Verification
4845

4946
#### Webhook configuration
5047

5148
Configure a Gitlab project with a webhook with a format like this: https://<receiver URL>:<receiver port>/webhooks/gitlab
5249

5350
#### Smoke test
54-
- Create an issue in the repo, you can see the logs in `receiver`, the `issue.created` event is generated.
5551

56-
You can test other events, but just validating that an issue.created event is generated in Kafka is enough to smoke test the receiver is set up properly.
52+
See above - the steps are the same for Github and Gitlab
5753

58-
#### Debugging
59-
You can re-run and debug the responses to webhook requests on Gitlab, in the configuration for the webhook. This can be useful if things aren't coming through properly in the receiver.
54+
## Debugging
55+
You can re-run and debug the responses to webhook requests on Github and Gitlab, in the configuration for the webhook. This can be useful if things aren't coming through properly in the receiver.

0 commit comments

Comments
 (0)