5db229fb45
Previously, only group masters could do this. However, project reporters can manage project labels, so there doesn't seem to be any need to restrict group labels further. Also, save a query or two by getting a single GroupMember object to find out if the user is a master or not.
66 lines
1.3 KiB
Ruby
66 lines
1.3 KiB
Ruby
class GroupMember < Member
|
|
SOURCE_TYPE = 'Namespace'.freeze
|
|
|
|
belongs_to :group, foreign_key: 'source_id'
|
|
|
|
delegate :update_two_factor_requirement, to: :user
|
|
|
|
# Make sure group member points only to group as it source
|
|
default_value_for :source_type, SOURCE_TYPE
|
|
validates :source_type, format: { with: /\ANamespace\z/ }
|
|
default_scope { where(source_type: SOURCE_TYPE) }
|
|
|
|
after_create :update_two_factor_requirement, unless: :invite?
|
|
after_destroy :update_two_factor_requirement, unless: :invite?
|
|
|
|
def self.access_level_roles
|
|
Gitlab::Access.options_with_owner
|
|
end
|
|
|
|
def self.access_levels
|
|
Gitlab::Access.sym_options_with_owner
|
|
end
|
|
|
|
def group
|
|
source
|
|
end
|
|
|
|
# Because source_type is `Namespace`...
|
|
def real_source_type
|
|
'Group'
|
|
end
|
|
|
|
private
|
|
|
|
def send_invite
|
|
notification_service.invite_group_member(self, @raw_invite_token)
|
|
|
|
super
|
|
end
|
|
|
|
def post_create_hook
|
|
notification_service.new_group_member(self)
|
|
|
|
super
|
|
end
|
|
|
|
def post_update_hook
|
|
if access_level_changed?
|
|
notification_service.update_group_member(self)
|
|
end
|
|
|
|
super
|
|
end
|
|
|
|
def after_accept_invite
|
|
notification_service.accept_group_invite(self)
|
|
|
|
super
|
|
end
|
|
|
|
def after_decline_invite
|
|
notification_service.decline_group_invite(self)
|
|
|
|
super
|
|
end
|
|
end
|