BigW Consortium Gitlab

  1. 27 Nov, 2016 1 commit
  2. 25 Nov, 2016 3 commits
  3. 21 Nov, 2016 1 commit
  4. 18 Nov, 2016 1 commit
  5. 17 Nov, 2016 2 commits
  6. 16 Nov, 2016 1 commit
  7. 14 Nov, 2016 1 commit
  8. 11 Nov, 2016 1 commit
  9. 09 Nov, 2016 2 commits
  10. 04 Nov, 2016 1 commit
  11. 03 Nov, 2016 2 commits
  12. 26 Oct, 2016 1 commit
  13. 19 Oct, 2016 7 commits
  14. 17 Oct, 2016 1 commit
  15. 11 Oct, 2016 1 commit
  16. 07 Oct, 2016 1 commit
    • Add markdown cache columns to the database, but don't use them yet · e94cd6fd
      Nick Thomas authored
      This commit adds a number of _html columns and, with the exception of Note,
      starts updating them whenever the content of their partner fields changes.
      
      Note has a collision with the note_html attr_accessor; that will be fixed later
      
      A background worker for clearing these cache columns is also introduced - use
      `rake cache:clear` to set it off. You can clear the database or Redis caches
      separately by running `rake cache:clear:db` or `rake cache:clear:redis`,
      respectively.
  17. 29 Sep, 2016 1 commit
  18. 28 Sep, 2016 1 commit
    • 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: 's avatarRémy Coutable <remy@rymai.me>
  19. 26 Sep, 2016 1 commit
  20. 20 Sep, 2016 3 commits
  21. 16 Sep, 2016 1 commit
  22. 13 Sep, 2016 1 commit
  23. 12 Sep, 2016 1 commit
  24. 07 Sep, 2016 1 commit
  25. 06 Sep, 2016 1 commit
  26. 01 Sep, 2016 1 commit
  27. 24 Aug, 2016 1 commit