Commit 6180a6af authored by Amy Qualls's avatar Amy Qualls

Merge branch 'docs-file-hooks-note-rem' into 'master'

Removed concurrent notes from File hooks page

See merge request gitlab-org/gitlab!72431
parents c6d28fb7 86c1be90
...@@ -7,16 +7,15 @@ type: reference ...@@ -7,16 +7,15 @@ type: reference
# File hooks **(FREE SELF)** # File hooks **(FREE SELF)**
> - Introduced in GitLab 10.6. > Renamed feature from Plugins to File hooks in GitLab 12.8.
> - Until GitLab 12.8, the feature name was Plugins.
With custom file hooks, GitLab administrators can introduce custom integrations With custom file hooks, GitLab administrators can introduce custom integrations
without modifying the GitLab source code. without modifying the GitLab source code.
NOTE: A file hook runs on each event. You can filter events or projects
Instead of writing and supporting your own file hook you can make changes in a file hook's code, and create many file hooks as you need. Each file hook is
directly to the GitLab source code and contribute back upstream. This way we can triggered by GitLab asynchronously in case of an event. For a list of events
ensure functionality is preserved across versions and covered by tests. see the [system hooks](../system_hooks/system_hooks.md) documentation.
NOTE: NOTE:
File hooks must be configured on the file system of the GitLab server. Only GitLab File hooks must be configured on the file system of the GitLab server. Only GitLab
...@@ -24,10 +23,9 @@ server administrators can complete these tasks. Explore ...@@ -24,10 +23,9 @@ server administrators can complete these tasks. Explore
[system hooks](../system_hooks/system_hooks.md) or [webhooks](../user/project/integrations/webhooks.md) [system hooks](../system_hooks/system_hooks.md) or [webhooks](../user/project/integrations/webhooks.md)
as an option if you do not have file system access. as an option if you do not have file system access.
A file hook runs on each event. You can filter events or projects Instead of writing and supporting your own file hook, you can also make changes
in a file hook's code, and create many file hooks as you need. Each file hook is directly to the GitLab source code and contribute back upstream. In this way, we can
triggered by GitLab asynchronously in case of an event. For a list of events ensure functionality is preserved across versions and covered by tests.
see the [system hooks](../system_hooks/system_hooks.md) documentation.
## Setup ## Setup
...@@ -67,7 +65,7 @@ message is logged to: ...@@ -67,7 +65,7 @@ message is logged to:
- `log/file_hook.log` in a source installation. - `log/file_hook.log` in a source installation.
NOTE: NOTE:
Before 14.0 release, the filename was `plugin.log` In GitLab 13.12 and earlier, the filename was `plugin.log`
## Creating file hooks ## Creating file hooks
......
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