Read about our upcoming Code of Conduct on this issue

  1. 04 Feb, 2019 1 commit
  2. 16 Jan, 2019 1 commit
    • Alejandro Rodríguez's avatar
      Return max group access level in the projects API · c93c371b91f7
      Alejandro Rodríguez authored
      Currently if a project is inside a nested group and a user doesn't have
      specific permissions for that group but does have permissions on a
      parent group the `GET /projects/:id` API call will return the following
      permissions:
      
      ```json
      permissions: { project_access: null, group_access: null }
      ```
      
      It could also happen that the group specific permissions are of lower
      level than the ones the user has in parent groups. This patch makes it
      so that the permission returned for `group_access` is the highest from
      amongst the hierarchy, which is (ostensibly) the information that the
      API user is interested in for that field.
      c93c371b91f7
  3. 15 Jan, 2019 2 commits
  4. 18 Dec, 2018 1 commit
    • blackst0ne's avatar
      Update specs to rails5 format · 147d8e55c2df
      blackst0ne authored
      Updates specs to use new rails5 format.
      
      The old format:
      `get :show, { some: params }, { some: headers }`
      
      The new format:
      `get :show, params: { some: params }, headers: { some: headers }`
      147d8e55c2df
  5. 06 Dec, 2018 1 commit
  6. 26 Oct, 2018 1 commit
  7. 19 Oct, 2018 1 commit
    • Bob Van Landuyt's avatar
      Remove the `ForkedProjectLink` model · b055a9ce0a40
      Bob Van Landuyt authored
      This removes the `ForkedProjectLink` model that has been replaced by
      the `ForkNetworkMember` and `ForkNetwork` combination. All existing
      relations have been adjusted to use these new models.
      
      The `forked_project_link` table has been dropped.
      
      The "Forks" count on the admin dashboard has been updated to count all
      `ForkNetworkMember` rows and deduct the number of `ForkNetwork`
      rows. This is because now the "root-project" of a fork network also
      has a `ForkNetworkMember` row. This count could become inaccurate when
      the root of a fork network is deleted.
      b055a9ce0a40
  8. 12 Sep, 2018 2 commits
  9. 21 Aug, 2018 1 commit
  10. 20 Aug, 2018 1 commit
  11. 16 Aug, 2018 1 commit
  12. 03 Aug, 2018 1 commit
  13. 23 Jul, 2018 2 commits
  14. 16 Jul, 2018 1 commit
  15. 11 Jul, 2018 1 commit
  16. 09 Jul, 2018 2 commits
  17. 27 Jun, 2018 1 commit
  18. 07 Jun, 2018 1 commit
  19. 22 May, 2018 1 commit
  20. 23 Apr, 2018 1 commit
  21. 13 Apr, 2018 1 commit
  22. 04 Apr, 2018 1 commit
  23. 26 Mar, 2018 1 commit
  24. 16 Feb, 2018 1 commit
    • Nick Thomas's avatar
      Fix order dependencies in some specs · b52c5ebf6976
      Nick Thomas authored
      Our automatically-generated project paths are of the form project<N>. If a spec
      manually specifies a project path of that form, it may conflict with the
      automatically-generated paths in some circumstances.
      b52c5ebf6976
  25. 07 Feb, 2018 1 commit
  26. 02 Feb, 2018 1 commit
  27. 19 Jan, 2018 1 commit
  28. 22 Dec, 2017 1 commit
  29. 16 Nov, 2017 1 commit
  30. 09 Nov, 2017 1 commit
  31. 06 Nov, 2017 1 commit
  32. 20 Oct, 2017 1 commit
  33. 07 Oct, 2017 1 commit
  34. 26 Sep, 2017 1 commit
  35. 19 Sep, 2017 1 commit
  36. 14 Sep, 2017 1 commit