delta/gitlab/gitlab-ce.git/app/mailers, branch gitlab-git-duplicate-code

Add DNS verification to Pages custom domains

2018-02-23T12:22:29+00:00

Resolve "group request membership mail with too long list of "To:""

2018-02-19T17:47:08+00:00

use Gitlab::UserSettings directly as a singleton instead of including/extending it

2018-02-02T18:39:55+00:00

Initial work to add notification reason to emails

2018-01-17T01:17:55+00:00

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.

Make discussion mail References all notes in the discussion

2017-12-13T20:26:01+00:00

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.

Make mail notifications of discussion notes In-Reply-To of each other

2017-12-13T20:26:01+00:00

When a note is part of a discussion, the email sent out should be
`In-Reply-To` the previous note in that discussion.

Closes gitlab-org/gitlab-ce#36054

Send a confirmation email when the user adds a secondary email address. Utilizes the Devise `confirmable` capabilities. Issue #37385

2017-09-23T13:23:11+00:00

`current_application_settings` belongs on `Gitlab::CurrentSettings`

2017-08-31T12:38:33+00:00

The initializers including this were doing so at the top level, so every object
loaded after them had a `current_application_settings` method. However, if
someone had rack-attack enabled (which was loaded before these initializers), it
would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
have that method.

To fix this:

1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
   `Object.new.current_application_settings` to work.
2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
   like that in several places.
3. Change the initializers to use that new form.

Speed up Group#user_ids_for_project_authorizations

2017-08-14T11:47:15+00:00

Rename many path_with_namespace -> full_path

2017-08-01T05:26:58+00:00