From 7696c4629d5fbc8e699b12b2b0b799a8b3f496f9 Mon Sep 17 00:00:00 2001 From: osher Date: Mon, 20 Mar 2023 16:40:53 +0200 Subject: [PATCH] README - fix broken link :docs of gitlab webhooks --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ee68dcf..8a3d418 100644 --- a/README.md +++ b/README.md @@ -127,7 +127,7 @@ git2consul expects to be run on the same node as a Consul agent. git2consul exp } ``` -The above example illustrates a 2 repo git2consul setup: one repo lives in an on-premises Git solution and the other is hosted at Github. The hooks array under each repository defines how git2consul will be notified of changes. git2consul supports [Atlassian Stash](https://confluence.atlassian.com/display/STASH/POST+service+webhook+for+Stash), [Atlassian Bitbucket](https://confluence.atlassian.com/display/BITBUCKET/POST+hook+management), [GitHub](https://developer.github.com/v3/repos/hooks/), and [Gitlab](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/web_hooks/web_hooks.md) webhooks as well as a basic polling model. +The above example illustrates a 2 repo git2consul setup: one repo lives in an on-premises Git solution and the other is hosted at Github. The hooks array under each repository defines how git2consul will be notified of changes. git2consul supports [Atlassian Stash](https://confluence.atlassian.com/display/STASH/POST+service+webhook+for+Stash), [Atlassian Bitbucket](https://confluence.atlassian.com/display/BITBUCKET/POST+hook+management), [GitHub](https://developer.github.com/v3/repos/hooks/), and [Gitlab](https://docs.gitlab.com/ee/user/project/integrations/webhooks.html) webhooks as well as a basic polling model. Note that multiple webhooks can share the same port. The only constraint is that webhooks for different repos do not share the same port and path.