summaryrefslogtreecommitdiff
path: root/doc/system_hooks
diff options
context:
space:
mode:
authorMarcel Amirault <ravlen@gmail.com>2019-05-24 08:03:22 +0000
committerMarcel Amirault <ravlen@gmail.com>2019-06-10 01:10:17 +0000
commit20c66d6e29df21df437f3f11afd0dd5c1b1230fe (patch)
tree085149020a13d152b2b95a5ad0b49e3371f0a043 /doc/system_hooks
parent72611cbc3a81647cc7f93cd8a84ae3b9f37ec8c7 (diff)
downloadgitlab-ce-20c66d6e29df21df437f3f11afd0dd5c1b1230fe.tar.gz
SSOT edits to docs that are alone in root directories
Diffstat (limited to 'doc/system_hooks')
-rw-r--r--doc/system_hooks/system_hooks.md22
1 files changed, 17 insertions, 5 deletions
diff --git a/doc/system_hooks/system_hooks.md b/doc/system_hooks/system_hooks.md
index a3698d60f6d..f978b96a30e 100644
--- a/doc/system_hooks/system_hooks.md
+++ b/doc/system_hooks/system_hooks.md
@@ -1,3 +1,7 @@
+---
+type: reference
+---
+
# System hooks
Your GitLab instance can perform HTTP POST requests on the following events:
@@ -27,11 +31,7 @@ The triggers for most of these are self-explanatory, but `project_update` and `p
System hooks can be used, e.g. for logging or changing information in a LDAP server.
-> **Note:**
->
-> We follow the same structure from Webhooks for Push and Tag events, but we never display commits.
->
-> Same deprecations from Webhooks are valid here.
+NOTE: **Note:** We follow the same structure and deprecations as [Webhooks](../user/project/integrations/webhooks.md) for Push and Tag events, but we never display commits.
## Hooks request example
@@ -640,3 +640,15 @@ X-Gitlab-Event: System Hook
"refs":["refs/heads/master"]
}
```
+
+<!-- ## Troubleshooting
+
+Include any troubleshooting steps that you can foresee. If you know beforehand what issues
+one might have when setting this up, or when something is changed, or on upgrading, it's
+important to describe those, too. Think of things that may go wrong and include them here.
+This is important to minimize requests for support, and to avoid doc comments with
+questions that you know someone might ask.
+
+Each scenario can be a third-level heading, e.g. `### Getting error message X`.
+If you have none to add when creating a doc, leave this section in place
+but commented out to help encourage others to add to it in the future. -->