Commit graph

24 commits

Author SHA1 Message Date
YarNayar
99b01e2359 Send notification emails when push to a merge request
Closes #23460
2018-03-26 13:24:52 +01:00
Sean McGivern
e4952f1703 Merge branch '41532-email-reason' into 'master'
Show why a notification email was sent

Closes #41532 and #1366

See merge request gitlab-org/gitlab-ce!16160
2018-01-19 11:01:46 +00:00
Mario de la Ossa
23a20c20f8
Initial work to add notification reason to emails
Adds `#build_notification_recipients` to `NotificationRecipientService`
that returns the `NotificationRecipient` objects in order to be able to
access the new attribute `reason`.

This new attribute is used in the different notifier methods in order to
add the reason as a header: `X-GitLab-NotificationReason`.

Only the reason with the most priority gets sent.
2018-01-16 19:17:55 -06:00
Alexis Reigel
a2655e3fbd use sentence case for "Merge request events" 2018-01-04 09:33:41 +01:00
Cindy Pallares
20aab3c85f Add project and group notification settings info
Notification settings are described, but aren't mentioned where they
are or where to change them.
2017-05-19 17:24:58 -05:00
Sean McGivern
a1805cbcd5 Quiet pipeline emails
1. Never send a pipeline email to anyone other than the user who created
   the pipeline.
2. Only send pipeline success emails to people with the custom
   notification setting for enabled. Watchers and participants will
   never receive this.
3. When custom settings are unset (for new settings and legacy ones),
   act as if failed_pipeline is set.
2017-04-03 13:59:48 +01:00
Lin Jen-Shin
365cdd8fe0 Make successful pipeline emails off for watchers
Closes #24845
2017-01-05 19:22:47 +08:00
Lin Jen-Shin
3e75e453fb Try to cover more cases about receivers of pipeline notifications
Feedback:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6342#note_17981421
2016-11-09 00:29:47 +08:00
Lin Jen-Shin
9176a19e3d Add pipelines to notifications documentation 2016-11-03 20:41:51 +08:00
Nick Thomas
10af11f4fe Allow people to subscribe to mentions in updated MRs and Issues
This slightly changes the semantics of the 'New Issue' and 'New MR' events to
include new mentions in edited Mentionables.

An alternative would be to introduce 'Issue updated' and 'MR updated' events,
but that would lead to questions about why those events were only available
to new mentions, and not existing mentions as well, so hold off for now.
2016-08-15 15:16:46 +01:00
Felipe Artur
36d48120f6 merge master into issue_3359_3 2016-06-29 11:04:18 -03:00
Felipe Artur
e5aa902860 Merge master into issue_12758 2016-06-17 14:29:11 -03:00
Felipe Artur
89a2c8730b Implement custom notification level options 2016-06-15 11:47:50 -03:00
Felipe Artur
0cf0352303 Add notification settings documentation and update screenshot 2016-06-13 15:51:11 -03:00
Felipe Artur
fc9844e8e1 Update documentation 2016-05-17 21:54:06 -05:00
karen Carias
e0642b2743 fixed conflict 2015-08-10 16:14:03 -07:00
karen Carias
37b4cfea3a fixed conflict and comment 2015-08-10 16:05:59 -07:00
karen Carias
8344c79508 fixed conflict and comment 2015-08-10 16:03:10 -07:00
karen Carias
082467e8e6 Info about not receiving emails 2015-08-07 13:07:04 -07:00
Douwe Maan
c6799b0e1e Update notification docs 2015-08-06 12:16:05 +02:00
karen Carias
3d6e67e44e fixed notifications title 2015-07-13 10:36:29 -07:00
Ewan Edwards
ad6c372eee Fix a number of discovered typos, capitalization of developer and
product names, plus a couple of instances of bad Markdown markup.
2015-02-03 15:18:40 -08:00
Marin Jankovski
8e7da6455b Fix spelling mistakes in notifications document. 2014-10-14 16:12:22 +02:00
Marin Jankovski
30b803fa3f Add notifications documentation. 2014-10-14 16:01:45 +02:00