1. 14 3月, 2016 1 次提交
    • Z
      External Users · 42fcd388
      Zeger-Jan van de Weg 提交于
      The user has the rights of a public user execpt it can never create a project,
       group, or team. Also it cant view internal projects.
      42fcd388
  2. 12 3月, 2016 2 次提交
  3. 01 3月, 2016 2 次提交
  4. 25 2月, 2016 1 次提交
  5. 20 2月, 2016 2 次提交
  6. 10 2月, 2016 1 次提交
  7. 02 2月, 2016 1 次提交
  8. 09 1月, 2016 1 次提交
  9. 06 1月, 2016 1 次提交
  10. 03 1月, 2016 1 次提交
  11. 15 12月, 2015 2 次提交
  12. 09 12月, 2015 2 次提交
  13. 08 12月, 2015 1 次提交
  14. 18 11月, 2015 2 次提交
    • Y
      Refactor User#authorized_groups/projects · e116a356
      Yorick Peterse 提交于
      These methods no longer include public groups/projects (that don't
      belong to the actual user) as this is handled by the various finder
      classes now. This also removes the need for passing extra arguments.
      
      Note that memoizing was removed _explicitly_. For whatever reason doing
      so messes up the users controller to a point where it claims a certain
      user does _not_ have access to certain groups/projects when it does have
      access. Existing code shouldn't be affected as these methods are only
      called in ways that they'd run queries anyway (e.g. a combination of
      "any?" and "each" which would run 2 queries regardless of memoizing).
      e116a356
    • Y
      Refactor getting user groups/projects/contributions · 5fcd9986
      Yorick Peterse 提交于
      This new setup no longer loads any IDs into memory using "pluck",
      instead using SQL UNIONs to merge the various datasets together. This
      results in greatly improved query performance as well as a reduction of
      memory usage.
      
      The old setup was in particular problematic when requesting the
      authorized projects _including_ public/internal projects as this would
      result in roughly 65000 project IDs being loaded into memory. These IDs
      would in turn be passed to other queries.
      5fcd9986
  15. 14 11月, 2015 1 次提交
  16. 03 11月, 2015 1 次提交
    • Y
      Fixed User sorting specs · a2f8f9ad
      Yorick Peterse 提交于
      The descriptions were not accurate and one particular spec seemingly
      expected the wrong User row to be returned.
      a2f8f9ad
  17. 02 10月, 2015 2 次提交
  18. 30 9月, 2015 2 次提交
  19. 20 9月, 2015 1 次提交
  20. 06 9月, 2015 1 次提交
  21. 20 8月, 2015 1 次提交
  22. 05 8月, 2015 1 次提交
  23. 03 8月, 2015 1 次提交
  24. 24 7月, 2015 1 次提交
  25. 11 7月, 2015 1 次提交
  26. 24 6月, 2015 1 次提交
  27. 23 6月, 2015 1 次提交
  28. 22 6月, 2015 1 次提交
  29. 21 6月, 2015 1 次提交
  30. 20 6月, 2015 2 次提交
  31. 18 6月, 2015 1 次提交