Zero
Zero
Currently, only all comments can be disabled. Adding `noteable_type` field check around [/lib/Web.js#L52](https://github.com/YappyBots/YappyGitLab/blob/9ba599358e343bd123856031c88763f953e5abec/lib/Web.js#L52) should do the trick. Use case: Having only issues and their comments in channel A (for the...
Low priority for us, but it would be nice to have. Currently this kind of events is rejected by Yappy with HTTP status 403 and response body: `Invalid data. Plz...
Its current name is `merge_request/approval`. `object_attributes.iid` and `object_attributes.title` fields remain same. PS: in `/lib/Gitlab/Events/merge_request-approved.js`, data from `object_attributes` is stored in the `issue` variable, but it's a merge request :slightly_smiling_face:
POST data is the same as for non-confidential notes. `X-Gitlab-Event` is different - `Confidential Note Hook` instead of `Note Hook`. `object_attributes.noteable_type` field remain present.
As requested by **ajgeiss0702#0702** on Discord.  POST data is the same for both confidential and non-confidential issues. `X-Gitlab-Event` is different, however - `Confidential Issue Hook` instead of `Issue Hook`....
JSON won't tell who or why it was cancelled, assume it was made manually by any user with the access. Here's an example: ``` { "object_kind": "pipeline", "object_attributes": { "id":...