Read about our upcoming Code of Conduct on this issue

  1. 31 Aug, 2019 1 commit
  2. 23 Apr, 2019 1 commit
  3. 31 Jan, 2019 1 commit
  4. 25 Jan, 2019 1 commit
  5. 06 Dec, 2018 1 commit
    • Stan Hu's avatar
      Remove unnecessary includes of ShellAdapter · a3000dbddf80
      Stan Hu authored
      Determined by running the script:
      
      ```
      included = `git grep --name-only ShellAdapter`.chomp.split("\n")
      used = `git grep --name-only gitlab_shell`.chomp.split("\n")
      included - used
      ```
      a3000dbddf80
  6. 11 Sep, 2018 1 commit
  7. 07 Aug, 2018 1 commit
  8. 11 Jul, 2018 1 commit
  9. 26 Apr, 2018 1 commit
  10. 07 Mar, 2018 1 commit
  11. 11 Aug, 2017 2 commits
  12. 05 Jun, 2017 1 commit
    • Sean McGivern's avatar
      Allow group reporters to manage group labels · 6ee85cf8ea6a
      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.
      6ee85cf8ea6a
  13. 21 Apr, 2017 1 commit
  14. 23 Feb, 2017 2 commits
  15. 24 Oct, 2016 1 commit
  16. 20 Oct, 2016 2 commits
    • Callum Dryden's avatar
      Differentiate the expire from leave event · a5f30e491c69
      Callum Dryden authored
      At the moment we cannot see weather a user left a project due to their
      membership expiring of if they themselves opted to leave the project.
      This adds a new event type that allows us to make this differentiation.
      Note that is not really feasable to go back and reliably fix up the
      previous events. As a result the events for previous expire removals
      will remain the same however events of this nature going forward will be
      correctly represented.
      a5f30e491c69
    • Callum Dryden's avatar
      Differentiate the expire from leave event · f0cad1cadc69
      Callum Dryden authored
      At the moment we cannot see weather a user left a project due to their
      membership expiring of if they themselves opted to leave the project.
      This adds a new event type that allows us to make this differentiation.
      Note that is not really feasable to go back and reliably fix up the
      previous events. As a result the events for previous expire removals
      will remain the same however events of this nature going forward will be
      correctly represented.
      f0cad1cadc69
  17. 28 Sep, 2016 1 commit
    • Rémy Coutable's avatar
      Allow Member.add_user to handle access requesters · 44fe4f60aea6
      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>
      44fe4f60aea6
  18. 10 Aug, 2016 1 commit
  19. 04 Aug, 2016 1 commit
  20. 02 Aug, 2016 1 commit
  21. 01 Aug, 2016 1 commit
  22. 01 Jul, 2016 1 commit
  23. 18 Jun, 2016 1 commit
  24. 16 Jun, 2016 2 commits
  25. 14 Jun, 2016 3 commits
  26. 03 Jun, 2016 2 commits
  27. 30 May, 2016 1 commit
  28. 22 May, 2016 1 commit
  29. 21 May, 2016 1 commit
  30. 20 May, 2016 1 commit
  31. 09 May, 2016 1 commit
  32. 06 May, 2016 1 commit
  33. 30 Mar, 2016 1 commit