Skip to content
Snippets Groups Projects
  1. Feb 28, 2020
  2. Sep 13, 2019
  3. Aug 31, 2019
  4. Jul 29, 2019
  5. Jul 18, 2019
  6. May 13, 2019
  7. Apr 23, 2019
  8. Mar 25, 2019
    • Sean McGivern's avatar
      Remove N+1 queries from users autocomplete · c5f9b2be
      Sean McGivern authored
      Both of these were related to groups:
      
      1. We need to preload routes (using the `with_route` scope) if we're
         going to get the group's path.
      2. We were counting each group's members separately.
      
      They're in the same commit because the spec for N+1 detection wouldn't
      pass with only one of these fixes.
      c5f9b2be
  9. Jan 31, 2019
  10. Jan 25, 2019
  11. Aug 07, 2018
  12. Apr 26, 2018
  13. Aug 11, 2017
  14. Jun 05, 2017
    • Sean McGivern's avatar
      Allow group reporters to manage group labels · 5db229fb
      Sean McGivern authored
      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.
      5db229fb
  15. Apr 21, 2017
  16. Apr 06, 2017
  17. Feb 23, 2017
  18. Oct 24, 2016
  19. Sep 28, 2016
    • Rémy Coutable's avatar
      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
  20. Jun 18, 2016
  21. Jun 16, 2016
  22. Jun 14, 2016
  23. Jun 03, 2016
  24. May 09, 2016
  25. May 06, 2016
  26. Mar 30, 2016
  27. May 03, 2015
  28. Apr 14, 2015
  29. Jan 27, 2015
  30. Oct 09, 2014
  31. Sep 14, 2014
Loading