summaryrefslogtreecommitdiff
path: root/app/mailers
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@14-5-stable-eev14.5.0-rc42GitLab Bot2021-11-182-12/+15
|
* Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42GitLab Bot2021-09-203-17/+42
|
* Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42GitLab Bot2021-08-194-3/+29
|
* Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42GitLab Bot2021-07-204-6/+30
|
* Add latest changes from gitlab-org/gitlab@14-0-stable-eev14.0.0-rc42GitLab Bot2021-06-164-17/+33
|
* Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42GitLab Bot2021-05-199-19/+28
|
* Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43GitLab Bot2021-04-203-4/+31
|
* Add latest changes from gitlab-org/gitlab@13-10-stable-eev13.10.0-rc40GitLab Bot2021-03-165-10/+31
|
* Add latest changes from gitlab-org/gitlab@13-9-stable-eev13.9.0-rc42GitLab Bot2021-02-184-0/+45
|
* Add latest changes from gitlab-org/gitlab@13-8-stable-eev13.8.0-rc42Robert Speicher2021-01-205-7/+33
|
* Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42GitLab Bot2020-12-174-10/+19
|
* Add latest changes from gitlab-org/gitlab@13-6-stable-eev13.6.0-rc42GitLab Bot2020-11-196-49/+51
|
* Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42GitLab Bot2020-10-216-9/+66
|
* Add latest changes from gitlab-org/gitlab@13-4-stable-eeGitLab Bot2020-09-193-6/+48
|
* Add latest changes from gitlab-org/gitlab@13-3-stable-eeGitLab Bot2020-08-201-0/+11
|
* Add latest changes from gitlab-org/gitlab@13-2-stable-eeGitLab Bot2020-08-051-1/+16
|
* Add latest changes from gitlab-org/gitlab@13-2-stable-eeGitLab Bot2020-07-204-0/+116
|
* Add latest changes from gitlab-org/gitlab@13-1-stable-eeGitLab Bot2020-06-185-4/+47
|
* Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot2020-05-205-0/+46
|
* Add latest changes from gitlab-org/gitlab@12-10-stable-eeGitLab Bot2020-04-202-0/+18
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-04-141-0/+11
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-201-0/+13
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-272-0/+8
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-171-1/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-275-5/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-231-9/+7
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-092-3/+3
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-101-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-101-0/+12
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-061-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-124-19/+37
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-172-0/+29
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-308-33/+26
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-271-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-131-1/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-135-0/+10
|
* Add X-GitLab-NotificationReason header to note emailsadd-notification-reason-to-note-emailsSean McGivern2019-09-021-12/+13
| | | | | | The 'assigned' reason doesn't apply to notes, but the other two can ('mentioned' and 'own_activity'), so we can still use this for note emails.
* Merge branch 'master' of dev.gitlab.org:gitlab/gitlabhqRobert Speicher2019-08-291-0/+2
|\
| * Merge branch 'security-hide_merge_request_ids_on_emails' into 'master'GitLab Release Tools Bot2019-08-291-0/+2
| |\ | | | | | | | | | | | | Prevent disclosure of merge request id via email See merge request gitlab/gitlabhq!3313
| | * Prevent disclosure of merge request id via emailFelipe Artur2019-08-191-0/+2
| | | | | | | | | | | | | | | Do not disclosure merge request id via email for unauthorized users when closing issues.
* | | Fix issue due notification emails threading66524-issue-due-notification-emails-are-threaded-incorrectlyHeinrich Lee Yu2019-08-291-1/+1
|/ / | | | | | | | | It should not be a start to a new thread but rather a reply to an existing thread
* | Handle namespaced modelsAlex Kalderimis2019-08-211-2/+13
| | | | | | | | | | | | We encountered issues with setting module headers for namespaced models. These changes address this. We retain the namespacing, but transform the classnames to make them into safe email headers.
* | Rework retry strategy for remote mirrorsBob Van Landuyt2019-08-131-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | **Prevention of running 2 simultaneous updates** Instead of using `RemoteMirror#update_status` and raise an error if it's already running to prevent the same mirror being updated at the same time we now use `Gitlab::ExclusiveLease` for that. When we fail to obtain a lease in 3 tries, 30 seconds apart, we bail and reschedule. We'll reschedule faster for the protected branches. If the mirror already ran since it was scheduled, the job will be skipped. **Error handling: Remote side** When an update fails because of a `Gitlab::Git::CommandError`, we won't track this error in sentry, this could be on the remote side: for example when branches have diverged. In this case, we'll try 3 times scheduled 1 or 5 minutes apart. In between, the mirror is marked as "to_retry", the error would be visible to the user when they visit the settings page. After 3 tries we'll mark the mirror as failed and notify the user. We won't track this error in sentry, as it's not likely we can help it. The next event that would trigger a new refresh. **Error handling: our side** If an unexpected error occurs, we mark the mirror as failed, but we'd still retry the job based on the regular sidekiq retries with backoff. Same as we used to The error would be reported in sentry, since its likely we need to do something about it.
* Respect alt email when sending group access notifications63568-access-email-notifications-custom-emailMario de la Ossa2019-07-253-13/+24
| | | | | When sending access granted/rejected emails we should also respect custom emails set for groups/sub-groups
* Make pipeline emails respect group email setting63485-fix-pipeline-emails-to-use-group-settingHeinrich Lee Yu2019-07-231-11/+1
| | | | | When a user's notification email is set for a group, we should use that for pipeline emails
* Remove group in notification email subjectHeinrich Lee Yu2019-07-011-2/+2
| | | | | This reverts to previous behavior where we have the group only when we don't have a project
* Fix notes email with group-level notification emailSean McGivern2019-06-241-1/+1
| | | | | A Noteable doesn't have a group directly, unless it's an epic - we need to look for the project's group to find the right email address.
* Omit blocked admins from repository check e-mailssh-omit-blocked-admins-from-notificationStan Hu2019-06-121-1/+1
| | | | | | | Blocked admins should not receive notifications about failed repository checks. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63019
* Apply reviewer suggestionsweimeng-email-routingWei-Meng Lee2019-05-311-1/+1
|
* Move method into groupWei-Meng Lee2019-05-311-1/+1
|