Renovate: [feat] Possibility to notify about PR/MR creation via webhook (i.e. slack)

Created on 18 Apr 2019  路  3Comments  路  Source: renovatebot/renovate

What would you like Renovate to be able to do?
I would like to have possibility to configure renovate to notify on slack when PR/MR is created.

Describe the solution you'd like
Possibility to configure :

  • webhook url
  • secret in configuration file // env variable ? - not sure how it could be handled
  • message template

Describe alternatives you've considered
Notifications via email/reviewer - slack would fit better in my workflow.

help wanted priority-4-low feature

Most helpful comment

I think that providing a flexible way to configure webhooks for select events is a nice feature idea, although it鈥檚 a feature that could get quite complex quickly, Eg:

  • which events can trigger a webhooks
  • multiple webhook receivers
  • auth for webhooks

If there鈥檚 any other service with a similar approach to webhook configuration then it would certainly help to lock down requirements here.

  • Multiple events can trigger webhooks, Eg PR creation, PR updates, automerges, vulnerability PR creation, etc
  • each event can have more than one webhook receiver
  • presumably need configurable get vs post
  • need a configurable JSON body (eg field names, values)

All 3 comments

@grzesuav would linking to documentation how to integrate GitHub/GitLab/BitBucket with Slack address your use case?
https://slack.github.com
https://confluence.atlassian.com/bitbucket/bitbucket-cloud-for-slack-945096776.html
https://docs.gitlab.com/ee/user/project/integrations/slack.html

Or is there some renovate specific information that would be posted to Slack? (if so, what would that info be?)

@ChristianMurphy I know about gitlab/slack integration, however :

  • once enabled, it notifies about every MR even, like creation, merge, closed etc - this is too much spam
  • I would like to be notified only about renovate MR's, there is no possibility to configure it with existing apis (to limit MR events to specific author etc)

I think that providing a flexible way to configure webhooks for select events is a nice feature idea, although it鈥檚 a feature that could get quite complex quickly, Eg:

  • which events can trigger a webhooks
  • multiple webhook receivers
  • auth for webhooks

If there鈥檚 any other service with a similar approach to webhook configuration then it would certainly help to lock down requirements here.

  • Multiple events can trigger webhooks, Eg PR creation, PR updates, automerges, vulnerability PR creation, etc
  • each event can have more than one webhook receiver
  • presumably need configurable get vs post
  • need a configurable JSON body (eg field names, values)
Was this page helpful?
0 / 5 - 0 ratings

Related issues

Flydiverny picture Flydiverny  路  4Comments

jgarec picture jgarec  路  3Comments

Flydiverny picture Flydiverny  路  4Comments

OmgImAlexis picture OmgImAlexis  路  4Comments

Arcanemagus picture Arcanemagus  路  4Comments