1. 23 Feb, 2017 1 commit
  2. 24 Oct, 2016 1 commit
  3. 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
  4. 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
  5. 10 Aug, 2016 1 commit
  6. 04 Aug, 2016 1 commit
  7. 02 Aug, 2016 1 commit
  8. 01 Aug, 2016 1 commit
  9. 01 Jul, 2016 1 commit
  10. 18 Jun, 2016 1 commit
  11. 16 Jun, 2016 2 commits
  12. 14 Jun, 2016 3 commits
  13. 03 Jun, 2016 2 commits
  14. 30 May, 2016 1 commit
  15. 22 May, 2016 1 commit
  16. 21 May, 2016 1 commit
  17. 20 May, 2016 1 commit
  18. 09 May, 2016 1 commit
  19. 06 May, 2016 1 commit
  20. 30 Mar, 2016 1 commit
  21. 21 Jan, 2016 1 commit
  22. 03 May, 2015 1 commit
  23. 14 Apr, 2015 7 commits
  24. 15 Mar, 2015 1 commit
  25. 13 Feb, 2015 2 commits
  26. 27 Jan, 2015 1 commit
  27. 09 Oct, 2014 1 commit
  28. 03 Oct, 2014 1 commit