045c671533
Use bcc for pipeline emails because:
...
We use bcc here because we don't want to generate this emails for a
thousand times. This could be potentially expensive in a loop, and
recipients would contain all project watchers so it could be a lot.
2016-10-18 20:02:35 +08:00
7d97a22e86
Just show the first merge request we found, feedback:
...
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6019#note_16963209
2016-10-14 19:54:51 +08:00
b5f9d4c4bc
Introduce Pipeline#merge_requests_with_active_first,
...
Feedback:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6019#note_16956802
2016-10-14 19:13:11 +08:00
6b50c21140
skip the premailer compilation step since css is already inlined for the pipeline emails
2016-10-08 00:58:49 -05:00
a4d63a91a2
prevent pipeline emails from using the normal layout wrapper
2016-10-07 18:30:42 -05:00
9c931c63c9
include pipeline ref in subject line
2016-10-06 10:12:59 -05:00
60caeb14a7
update subject and email header message
2016-10-06 10:09:24 -05:00
db6b2b1899
Show open merge request against default branch if exists
2016-09-26 17:18:30 +08:00
4add6ca6ec
Try to integrate the email into notification system
2016-09-13 19:09:53 +08:00
5de54a7137
no longer TODO
2016-09-01 02:21:24 +08:00
1bd2327c31
Add mock email templates
2016-09-01 01:20:24 +08:00
9758233807
Fix copy pasta
2016-08-31 17:38:25 +08:00
34cbc51e23
Add a new pipeline email service. TODO: email templates and tests
2016-08-26 16:56:55 +08:00
Lin Jen-Shin