diff options
| author | Joe Marty <jmarty@iexposure.com> | 2017-10-19 19:18:03 +0300 |
|---|---|---|
| committer | Joe Marty <jmarty@iexposure.com> | 2017-10-20 20:13:35 +0300 |
| commit | 81eb4ad36827e6cb2090e8e2ae599e5a637910a4 (patch) | |
| tree | 7b032c573912fd19252090e74219ff24e65d6cec /doc/system_hooks | |
| parent | 490cce630f5984d063283537ac42a6f9fbad86e6 (diff) | |
Clarify the difference between project_update and project_rename
Diffstat (limited to 'doc/system_hooks')
| -rw-r--r-- | doc/system_hooks/system_hooks.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/system_hooks/system_hooks.md b/doc/system_hooks/system_hooks.md index 0399ebec86a..a45a4eb9e49 100644 --- a/doc/system_hooks/system_hooks.md +++ b/doc/system_hooks/system_hooks.md @@ -2,6 +2,8 @@ Your GitLab instance can perform HTTP POST requests on the following events: `project_create`, `project_destroy`, `project_rename`, `project_transfer`, `project_update`, `user_add_to_team`, `user_remove_from_team`, `user_create`, `user_destroy`, `key_create`, `key_destroy`, `group_create`, `group_destroy`, `user_add_to_group` and `user_remove_from_group`. +The triggers for most of these are self-explanatory, but `project_update` and `project_rename` deserve some clarification: `project_update` is fired any time an attribute of a project is changed (name, description, tags, etc.) *unless* the `path` attribute is also changed. In that case, a `project_rename` is triggered instead (so that, for instance, if all you care about is the repo URL, you can just listen for `project_rename`). + System hooks can be used, e.g. for logging or changing information in a LDAP server. > **Note:** |