@@ -13,6 +13,7 @@ Your GitLab instance can perform HTTP POST requests on the following events:
...
@@ -13,6 +13,7 @@ Your GitLab instance can perform HTTP POST requests on the following events:
-`project_update`
-`project_update`
-`user_add_to_team`
-`user_add_to_team`
-`user_remove_from_team`
-`user_remove_from_team`
-`user_update_for_team`
-`user_create`
-`user_create`
-`user_destroy`
-`user_destroy`
-`user_failed_login`
-`user_failed_login`
...
@@ -24,6 +25,7 @@ Your GitLab instance can perform HTTP POST requests on the following events:
...
@@ -24,6 +25,7 @@ Your GitLab instance can perform HTTP POST requests on the following events:
-`group_rename`
-`group_rename`
-`user_add_to_group`
-`user_add_to_group`
-`user_remove_from_group`
-`user_remove_from_group`
-`user_update_for_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`).
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`).
...
@@ -173,6 +175,26 @@ Please refer to `group_rename` and `user_rename` for that case.
...
@@ -173,6 +175,26 @@ Please refer to `group_rename` and `user_rename` for that case.