- 08 Aug, 2017 1 commit
-
-
Brian Neel authored
-
- 31 Jul, 2017 1 commit
-
-
Sean McGivern authored
This was migrated to separate columns in 9.4, and now just needs to be removed for real.
-
- 28 Jun, 2017 1 commit
-
-
Tiago Botelho authored
-
- 15 Jun, 2017 2 commits
-
-
Sean McGivern authored
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.
-
Sean McGivern authored
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.
-
- 07 Jun, 2017 1 commit
-
-
Yorick Peterse authored
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.
-
- 03 Apr, 2017 1 commit
-
-
Sean McGivern authored
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.
-
- 23 Feb, 2017 1 commit
-
-
Douwe Maan authored
-
- 05 Jan, 2017 1 commit
-
-
Lin Jen-Shin authored
for watchers. Feedback: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8176#note_20920905
-
- 17 Oct, 2016 1 commit
-
-
Lin Jen-Shin authored
This reverts commit 1404aa86.
-
- 14 Sep, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 13 Sep, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 07 Jul, 2016 1 commit
-
-
Sean McGivern authored
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.
-
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 13e37a3e.
-
James Lopez authored
-
- 15 Jun, 2016 1 commit
-
-
Felipe Artur authored
-
- 14 Jun, 2016 1 commit
-
-
Felipe Artur authored
-
- 13 Jun, 2016 3 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
Felipe Artur authored
-
- 10 Jun, 2016 1 commit
-
-
Felipe Artur authored
-
- 07 Jun, 2016 1 commit
-
-
Phil Hughes authored
This is part of #12758
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 09 May, 2016 1 commit
-
-
Jeroen van Baarsen authored
In 8278b763 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
-
- 06 May, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 11 Apr, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 08 Apr, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 30 Mar, 2016 3 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
* 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>
-
Dmitriy Zaporozhets authored
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>
-