Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-04-20 | Add latest changes from gitlab-org/gitlab@14-10-stable-eev14.10.0-rc42 | GitLab Bot | |
2022-03-18 | Add latest changes from gitlab-org/gitlab@14-9-stable-eev14.9.0-rc42 | GitLab Bot | |
2022-01-20 | Add latest changes from gitlab-org/gitlab@14-7-stable-eev14.7.0-rc42 | GitLab Bot | |
2021-12-20 | Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42 | GitLab Bot | |
2021-11-18 | Add latest changes from gitlab-org/gitlab@14-5-stable-eev14.5.0-rc42 | GitLab Bot | |
2021-09-20 | Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42 | GitLab Bot | |
2021-08-19 | Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42 | GitLab Bot | |
2021-07-20 | Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42 | GitLab Bot | |
2021-06-16 | Add latest changes from gitlab-org/gitlab@14-0-stable-eev14.0.0-rc42 | GitLab Bot | |
2021-05-19 | Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42 | GitLab Bot | |
2021-04-21 | Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43 | GitLab Bot | |
2021-03-16 | Add latest changes from gitlab-org/gitlab@13-10-stable-eev13.10.0-rc40 | GitLab Bot | |
2021-02-18 | Add latest changes from gitlab-org/gitlab@13-9-stable-eev13.9.0-rc42 | GitLab Bot | |
2021-01-20 | Add latest changes from gitlab-org/gitlab@13-8-stable-eev13.8.0-rc42 | Robert Speicher | |
2020-12-17 | Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42 | GitLab Bot | |
2020-11-19 | Add latest changes from gitlab-org/gitlab@13-6-stable-eev13.6.0-rc42 | GitLab Bot | |
2020-10-21 | Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42 | GitLab Bot | |
2020-09-19 | Add latest changes from gitlab-org/gitlab@13-4-stable-ee | GitLab Bot | |
2020-08-20 | Add latest changes from gitlab-org/gitlab@13-3-stable-ee | GitLab Bot | |
2020-08-05 | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | |
2020-07-20 | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | |
2020-06-18 | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | |
2020-05-20 | Add latest changes from gitlab-org/gitlab@13-0-stable-ee | GitLab Bot | |
2020-04-20 | Add latest changes from gitlab-org/gitlab@12-10-stable-ee | GitLab Bot | |
2020-04-14 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-20 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-27 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-28 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-23 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-09 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-11 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-30 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-27 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-02 | Add X-GitLab-NotificationReason header to note emails | Sean McGivern | |
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. | |||
2019-08-30 | Merge branch 'master' of dev.gitlab.org:gitlab/gitlabhq | Robert Speicher | |
2019-08-30 | Merge branch 'security-hide_merge_request_ids_on_emails' into 'master' | GitLab Release Tools Bot | |
Prevent disclosure of merge request id via email See merge request gitlab/gitlabhq!3313 | |||
2019-08-29 | Fix issue due notification emails threading | Heinrich Lee Yu | |
It should not be a start to a new thread but rather a reply to an existing thread | |||
2019-08-21 | Handle namespaced models | Alex Kalderimis | |
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. | |||
2019-08-19 | Prevent disclosure of merge request id via email | Felipe Artur | |
Do not disclosure merge request id via email for unauthorized users when closing issues. | |||
2019-08-13 | Rework retry strategy for remote mirrors | Bob Van Landuyt | |
**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. | |||
2019-07-26 | Respect alt email when sending group access notifications | Mario de la Ossa | |
When sending access granted/rejected emails we should also respect custom emails set for groups/sub-groups | |||
2019-07-23 | Make pipeline emails respect group email setting | Heinrich Lee Yu | |
When a user's notification email is set for a group, we should use that for pipeline emails | |||
2019-07-01 | Remove group in notification email subject | Heinrich Lee Yu | |
This reverts to previous behavior where we have the group only when we don't have a project |