When setting up the service I was not sure which webhook I should use, by adding
this Help text I hope we can help people in the future with setting up this hook
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
Supports four different event types all bundled under the "note" event type:
- comments on a commit
- comments on an issue
- comments on a merge request
- comments on a code snippet
1) Adds a DB migration for all services to toggle on push, issue, and merge events.
2) Upon an issue or merge request event, fire service hooks.
3) Slack service supports custom messages for each of these events. Other services
not supported at the moment.
4) Label merge request hooks with their corresponding actions.
per changes with slack, they’re now using “static” web hook urls that describe the team & service with IDs that don’t change if the team or service name change. their recommendation is to use the raw webhook_url instead of building it out of components to allow more flexibility
this should also prevent issues cropping up with mistakes in how the urls are parsed
Jeroen van Baarsen