Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add latest changes from gitlab-org/gitlab@15-6-stable-eev15.6.0-rc42 | GitLab Bot | 2022-11-17 | 1 | -3/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42 | GitLab Bot | 2021-08-19 | 1 | -3/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42 | GitLab Bot | 2021-05-19 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43 | GitLab Bot | 2021-04-20 | 1 | -0/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-10-stable-eev13.10.0-rc40 | GitLab Bot | 2021-03-16 | 1 | -1/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42 | GitLab Bot | 2020-12-17 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42 | GitLab Bot | 2020-10-21 | 1 | -0/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-3-stable-ee | GitLab Bot | 2020-08-20 | 1 | -2/+7 |
| | |||||
* | Add latest changes from gitlab-org/security/gitlab@13-0-stable-ee | GitLab Bot | 2020-05-26 | 1 | -0/+8 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-27 | 1 | -3/+11 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-06 | 1 | -0/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-29 | 1 | -1/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-18 | 1 | -0/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-17 | 1 | -0/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-13 | 1 | -0/+2 |
| | |||||
* | Remove ignore_column occurence in CE coderemove-old-ignore-column | Dmitriy Zaporozhets | 2019-09-10 | 1 | -2/+0 |
| | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | ||||
* | Use self.ignored_columns += instead of = | Stan Hu | 2019-08-30 | 1 | -2/+1 |
| | | | | This is to accomodate prepended modules. | ||||
* | Remove dependency on IgnorableColumn concern | dineshpanda | 2019-08-30 | 1 | -2/+1 |
| | |||||
* | Simplify notification check for participatingsimplify-pipeline-notification-check | Heinrich Lee Yu | 2019-06-06 | 1 | -6/+3 |
| | |||||
* | Inherit from ApplicationRecord instead of ActiveRecord::Base | Nick Thomas | 2019-03-28 | 1 | -1/+1 |
| | |||||
* | reorder notification settings by noisy-ness | C.J. Jameson | 2018-11-30 | 1 | -1/+1 |
| | | | | fixes !54609 | ||||
* | Move N_ calls into separate files | Mark Chao | 2018-08-14 | 1 | -0/+1 |
| | | | | | | These are dynamic translations, so has to be marked explicitly using `N_`, but they are not used in runtime, so can exist in separate file. https://github.com/grosser/gettext_i18n_rails#unfound-translations-with-rake-gettextfind | ||||
* | Add email_events to replace EMAIL_EVENTS because it needs to be dynamic, | Mark Chao | 2018-08-14 | 1 | -0/+8 |
| | | | allowing override for EE. | ||||
* | Enable frozen string in app/models/*.rbrepo-forks/gitlab-ce-frozen-string-enable-app-models | gfyoung | 2018-07-26 | 1 | -0/+2 |
| | | | | Partially addresses #47424. | ||||
* | Allow to toggle notifications for issues due soon | Felipe Artur | 2018-07-12 | 1 | -0/+1 |
| | |||||
* | Only send issue due emails to participants and custom subscribers | Sean McGivern | 2018-03-30 | 1 | -1/+2 |
| | |||||
* | Send notification emails when push to a merge requestYarNayar/gitlab-ce-23460-send-email-when-pushing-more-commits-to-the-merge-request | YarNayar | 2018-03-26 | 1 | -1/+6 |
| | | | | Closes #23460 | ||||
* | Re-enable SqlInjection and CommandInjection | Brian Neel | 2017-08-08 | 1 | -1/+1 |
| | |||||
* | Remove events column from notification settings33620-remove-events-from-notification_settings | Sean McGivern | 2017-07-31 | 1 | -29/+5 |
| | | | | | This was migrated to separate columns in 9.4, and now just needs to be removed for real. | ||||
* | Fix current feature related specs | Tiago Botelho | 2017-06-28 | 1 | -1/+1 |
| | |||||
* | Deserialise existing custom notification settingsdeserialize-custom-notifications | Sean McGivern | 2017-06-15 | 1 | -2/+24 |
| | | | | | | Create a post-deployment migration to update all existing notification settings with at least one custom level enabled to the new format. Also handle the same conversion when updating settings, to catch any stragglers. | ||||
* | Add columns for custom notification settings | Sean McGivern | 2017-06-15 | 1 | -18/+7 |
| | | | | | | Add columns for each custom notification level, defaulting to null. Read from those columns if non-null, otherwise fall back to the serialized column. Writing will write to the new column if `events` isn't manually set. | ||||
* | Added Cop to blacklist polymorphic associations | Yorick Peterse | 2017-06-07 | 1 | -1/+1 |
| | | | | | | | | One should really use a separate table instead of using polymorphic associations. See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11168 for more information. | ||||
* | Quiet pipeline emailsquiet-pipelines | Sean McGivern | 2017-04-03 | 1 | -4/+13 |
| | | | | | | | | | | 1. Never send a pipeline email to anyone other than the user who created the pipeline. 2. Only send pipeline success emails to people with the custom notification setting for enabled. Watchers and participants will never receive this. 3. When custom settings are unset (for new settings and legacy ones), act as if failed_pipeline is set. | ||||
* | Enable Style/MutableConstant | Douwe Maan | 2017-02-23 | 1 | -2/+2 |
| | |||||
* | Introduce EXCLUDED_WATCHER_EVENTS to exclude eventsremove-successful-pipeline-emails-for-now | Lin Jen-Shin | 2017-01-05 | 1 | -0/+4 |
| | | | | | for watchers. Feedback: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8176#note_20920905 | ||||
* | Revert "Split notification integration into another branch" | Lin Jen-Shin | 2016-10-17 | 1 | -1/+3 |
| | | | | This reverts commit 1404aa8677969a03ed56e8f8350257f317f576d8. | ||||
* | Split notification integration into another branch | Lin Jen-Shin | 2016-09-14 | 1 | -3/+1 |
| | |||||
* | Try to integrate the email into notification system | Lin Jen-Shin | 2016-09-13 | 1 | -1/+3 |
| | |||||
* | Exclude projects pending delete from notifications | Sean McGivern | 2016-07-07 | 1 | -1/+8 |
| | | | | | | | If the Sidekiq job fails for some reason, a project can be 'stuck' pending deletion. The project can't be viewed, so it shouldn't be available through the notification settings association as this will throw an exception when we try to show the link. | ||||
* | Implement custom notification level options | Felipe Artur | 2016-06-15 | 1 | -1/+36 |
| | |||||
* | Remove notification level from user model | Felipe Artur | 2016-06-10 | 1 | -1/+0 |
| | |||||
* | Notifications dropdown on project page now has descriptions | Phil Hughes | 2016-06-07 | 1 | -1/+1 |
| | | | | This is part of #12758 | ||||
* | Remove the annotate gem and delete old annotations | Jeroen van Baarsen | 2016-05-09 | 1 | -13/+0 |
| | | | | | | | | | In 8278b763d96ef10c6494409b18b7eb541463af29 the default behaviour of annotation has changes, which was causing a lot of noise in diffs. We decided in #17382 that it is better to get rid of the whole annotate gem, and instead let people look at schema.rb for the columns in a table. Fixes: #17382 | ||||
* | Annotate the models | Zeger-Jan van de Weg | 2016-05-06 | 1 | -0/+13 |
| | |||||
* | Use Hash instead of Array on NotificationSetting#level enum | Douglas Barbosa Alexandre | 2016-04-11 | 1 | -3/+1 |
| | |||||
* | Use default_value_for to set default NotificationSetting#level | Douglas Barbosa Alexandre | 2016-04-08 | 1 | -8/+6 |
| | |||||
* | Refactor creating notification setting with defaults | Dmitriy Zaporozhets | 2016-03-30 | 1 | -0/+11 |
| | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | ||||
* | Introduce NotificationSetting to user interface | Dmitriy Zaporozhets | 2016-03-30 | 1 | -0/+7 |
| | | | | | | | | * visiting project will create notification setting if missing * change notification setting per project even without membership * use notification settings instead of membership on profile page Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> | ||||
* | Introduce NotificationSetting model | Dmitriy Zaporozhets | 2016-03-30 | 1 | -0/+14 |
It will hold notification setting per group or per project. It will allow get rid of notification level stored in Member model Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> |