- 17 Jan, 2018 1 commit
-
-
Mario de la Ossa authored
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.
-
- 22 Dec, 2017 1 commit
-
-
blackst0ne authored
-
- 13 Dec, 2017 1 commit
-
-
Toon Claes authored
When a note is part of a discussion, the email sent out will be `In-Reply-To` the previous note in that discussion. It also `References` all the previous notes in that discussion, and the original issue. Closes gitlab-org/gitlab-ce#36054.
-
- 01 Dec, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 13 Nov, 2017 1 commit
-
-
Felipe Artur authored
-
- 09 Oct, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 23 Sep, 2017 1 commit
-
-
Brett Walker authored
Send a confirmation email when the user adds a secondary email address. Utilizes the Devise `confirmable` capabilities. Issue #37385
-
- 01 Sep, 2017 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 10 Aug, 2017 1 commit
-
-
Robert Speicher authored
-
- 02 Aug, 2017 1 commit
-
-
Robert Speicher authored
-
- 27 Jul, 2017 1 commit
-
-
Alexis Reigel authored
-
- 05 Jul, 2017 1 commit
-
-
Douwe Maan authored
-
- 21 Jun, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 14 Jun, 2017 1 commit
-
-
Robert Speicher authored
-
- 25 May, 2017 1 commit
-
-
Ruben Davila authored
There was a race condition issue when the application was generating an email and was using a language that was previously being used in other request.
-
- 04 May, 2017 1 commit
-
-
Valery Sizov authored
-
- 01 May, 2017 1 commit
-
-
Robert Speicher authored
-
- 26 Apr, 2017 1 commit
-
-
Sean McGivern authored
- Ignore JS fixtures - Ignore qa directory - Rewrite concern specs to put concern name first
-
- 06 Apr, 2017 1 commit
-
-
Toon Claes authored
Visit `/rails/mailers/notify` on your local running GitLab instance to show a preview pipeline success emails.
-
- 05 Apr, 2017 5 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 03 Apr, 2017 1 commit
-
-
Rémy Coutable authored
FFaker can generate data that randomly break our test suite. This simplifies our factories and use sequences which are more predictive. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 27 Mar, 2017 1 commit
-
-
Robert Speicher authored
-
- 21 Mar, 2017 2 commits
-
-
Robert Speicher authored
We perform a bunch of setup for most of these cases, and it didn't make sense to do an entirely new costly setup just to test a different string in the same body of the email we just generated in the last test.
-
Robert Speicher authored
This shared example was only used by this spec so having it in a separate file provided no benefit, at the cost of clarity. This also reduces the three `it` blocks into a single test with `aggregate_failures`.
-
- 17 Mar, 2017 2 commits
-
-
Kamil Trzciński authored
-
Rémy Coutable authored
This solves transient failures when a text contains HTML-escapable characters such as `'`. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 14 Mar, 2017 1 commit
-
-
Nick Thomas authored
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
- 28 Nov, 2016 3 commits
-
-
Ruben Davila authored
This new global setting will allow admins to specify if HTML emails should be sent or not, this is basically useful when system administrators want to save some disk space by avoiding emails in HTML format and using only the Plain Text version.
-
Sean McGivern authored
-
Sean McGivern authored
-
- 25 Nov, 2016 3 commits
-
-
hhoopes authored
-
hhoopes authored
* Added keyword arguments to truncated_diff_lines method to allow for using highlighting or not (html templates vs. text) * Tweaked templates for consistency and format appropriateness
-
hhoopes authored
Previously the `truncated_diff_lines` method for outputting a discussion diff took in already highlighted lines, which meant it wasn't reuseable for truncating ANY lines. In the way it was used, it also meant that for any email truncation, the whole diff was being highlighted before being truncated, meaning wasted time highlighting lines that wouldn't even be used (granted, they were being memoized, so perhaps this wasn't that great of an issue). I refactored truncation away from highlighting, in order to truncate formatted diffs for text templates in email, using `>`s to designate each line, but otherwise retaining the parsing already done to create `diff_lines`. Additionally, while notes on merge requests or commits had already been tested, there was no existing test for notes on a diff on an MR or commit. Added mailer tests for such, and a unit test for truncating diff lines.
-