Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

project_team.rb

  • Rémy Coutable's avatar
    ec0061a9
    Allow Member.add_user to handle access requesters · ec0061a9
    Rémy Coutable authored
    
    Changes include:
    
    - Ensure Member.add_user is not called directly when not necessary
    - New GroupMember.add_users_to_group to have the same abstraction level as for Project
    - Refactor Member.add_user to take a source instead of an array of members
    - Fix Rubocop offenses
    - Always use Project#add_user instead of project.team.add_user
    - Factorize users addition as members in Member.add_users_to_source
    - Make access_level a keyword argument in GroupMember.add_users_to_group and ProjectMember.add_users_to_projects
    - Destroy any requester before adding them as a member
    - Improve the way we handle access requesters in Member.add_user
      Instead of removing the requester and creating a new member,
      we now simply accepts their access request. This way, they will
      receive a "access request granted" email.
    - Fix error that was previously silently ignored
    - Stop raising when access level is invalid in Member, let Rails validation do their work
    
    Signed-off-by: default avatarRémy Coutable <remy@rymai.me>
    ec0061a9
    History
    Allow Member.add_user to handle access requesters
    Rémy Coutable authored
    
    Changes include:
    
    - Ensure Member.add_user is not called directly when not necessary
    - New GroupMember.add_users_to_group to have the same abstraction level as for Project
    - Refactor Member.add_user to take a source instead of an array of members
    - Fix Rubocop offenses
    - Always use Project#add_user instead of project.team.add_user
    - Factorize users addition as members in Member.add_users_to_source
    - Make access_level a keyword argument in GroupMember.add_users_to_group and ProjectMember.add_users_to_projects
    - Destroy any requester before adding them as a member
    - Improve the way we handle access requesters in Member.add_user
      Instead of removing the requester and creating a new member,
      we now simply accepts their access request. This way, they will
      receive a "access request granted" email.
    - Fix error that was previously silently ignored
    - Stop raising when access level is invalid in Member, let Rails validation do their work
    
    Signed-off-by: default avatarRémy Coutable <remy@rymai.me>