From b5705fedfc391b59d4d4a58dd16a939fd171b478 Mon Sep 17 00:00:00 2001 From: Justin Tobler <jtobler@gitlab.com> Date: Wed, 6 Dec 2023 00:43:02 +0000 Subject: [PATCH] doc/hooks: Clarify how administrators configure server hooks In GitLab 15.11 a new Gitaly CLI command was introduced to enable administrators to more easily set custom Git hooks for individual repositories in Gitaly. This replaces the need for administrators to set hooks directly on the file system. Update the documentation to mention using the Gitaly CLI instead. --- doc/administration/server_hooks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/administration/server_hooks.md b/doc/administration/server_hooks.md index 61ed5d751ec49..3abd18bec9adc 100644 --- a/doc/administration/server_hooks.md +++ b/doc/administration/server_hooks.md @@ -18,8 +18,8 @@ on the GitLab server. You can use them to run Git-related tasks such as: Git server hooks use `pre-receive`, `post-receive`, and `update` [Git server-side hooks](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks#_server_side_hooks). -GitLab administrators configure server hooks on the file system of the GitLab server. If you don't have file system access, -alternatives to server hooks include: +GitLab administrators configure server hooks through the Gitaly CLI, which connects to the Gitaly gRPC API. +If you don't have access to the Gitaly CLI, alternatives to server hooks include: - [Webhooks](../user/project/integrations/webhooks.md). - [GitLab CI/CD](../ci/index.md). -- GitLab