Commit 0c8bbd07 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Move hook name note to the top

parent 54579baf
...@@ -50,6 +50,9 @@ Hooks can be also placed in `hooks/<hook_name>.d` (global) or ...@@ -50,6 +50,9 @@ Hooks can be also placed in `hooks/<hook_name>.d` (global) or
`custom_hooks/<hook_name>.d` (per project) directories supporting chained `custom_hooks/<hook_name>.d` (per project) directories supporting chained
execution of the hooks. execution of the hooks.
NOTE: **Note:** `<hook_name>.d` would need to be either `pre-receive.d`,
`post-receive.d`, or `update.d` to work properly. Any other names will be ignored.
To look in a different directory for the global custom hooks (those in To look in a different directory for the global custom hooks (those in
`hooks/<hook_name.d>`), set `custom_hooks_dir` in gitlab-shell config. For `hooks/<hook_name.d>`), set `custom_hooks_dir` in gitlab-shell config. For
Omnibus installations, this can be set in `gitlab.rb`; and in source Omnibus installations, this can be set in `gitlab.rb`; and in source
...@@ -69,8 +72,6 @@ pattern (`*~`). ...@@ -69,8 +72,6 @@ pattern (`*~`).
The hooks of the same type are executed in order and execution stops on the The hooks of the same type are executed in order and execution stops on the
first script exiting with a non-zero value. first script exiting with a non-zero value.
> **Note:** In the above examples, `<hook_name>.d` would need to be either `pre-receive.d`, `post-receive.d`, or `update.d` to work properly. Any other names would be ignored.
## Custom error messages ## Custom error messages
> [Introduced][5073] in GitLab 8.10. > [Introduced][5073] in GitLab 8.10.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment