Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2017-07-31Remove events column from notification settingsSean McGivern
This was migrated to separate columns in 9.4, and now just needs to be removed for real.
2017-07-27Remove superfluous type defs in specsKeifer Furzland
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-07-24Adjust tests to work with latest shoulda gemDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2017-07-24Update tests for new version of shoulda-matchersDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2017-06-15Deserialise existing custom notification settingsSean McGivern
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.
2016-07-07Exclude projects pending delete from notificationsSean McGivern
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.
2016-06-15Implement custom notification level optionsFelipe Artur
2016-06-10Remove notification level from user modelFelipe Artur
2016-03-30Add spec for user_id uniq in NotificationSetting modelDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2016-03-30Small refactoring and cleanup of notification logicDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2016-03-30Introduce NotificationSetting modelDmitriy Zaporozhets
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>