1. 26 9月, 2019 1 次提交
  2. 25 9月, 2019 1 次提交
  3. 24 9月, 2019 1 次提交
  4. 16 9月, 2019 1 次提交
  5. 07 9月, 2019 1 次提交
  6. 03 9月, 2019 1 次提交
  7. 09 8月, 2019 1 次提交
  8. 03 7月, 2019 1 次提交
  9. 21 5月, 2019 1 次提交
  10. 15 5月, 2019 2 次提交
    • A
      Move issue details to from IssueBasic to Issue entity · a4fbf39e
      Alexandru Croitor 提交于
      Cleanup IssueBasic entity to keep it basic and move extra attributes
      to Issue entity which contains more details
      a4fbf39e
    • A
      Changes to issues api · 5ec28dc3
      Alexandru Croitor 提交于
      When issues_controller endpoint was used for search, the parameters
      passed to the controller were slightly different then the ones
      passed to API. Because the searchbar UI is reused in different
      places and builds the parameters passed to request in same way
      we need to account for old parameter names.
      
      
      Add issues_statistics api endpoints
      
      Adds issue_statistics api endpoints for issue lists and returns
      counts of issues for all, closed and opened states.
      
      
      Expose more label attributes based on a param
      
      When requesting issues list through API expose more attributes
      for labels, like color, description if with_labels_data param is
      being passed, avoiding this way to change response schema for users
      that already use API.
      
      https://gitlab.com/gitlab-org/gitlab-ce/issues/57402
      5ec28dc3
  11. 03 5月, 2019 1 次提交
    • K
      Allow guests users to access project releases · 241ba4be
      Krasimir Angelov 提交于
      This is step one of resolving
      https://gitlab.com/gitlab-org/gitlab-ce/issues/56838.
      
      Here is what changed:
      - Revert the security fix from bdee9e84.
      - Do not leak repository information (tag name, commit) to guests in API
      responses.
      - Do not include links to source code in API responses for users that do
      not have download_code access.
      - Show Releases in sidebar for guests.
      - Do not display links to source code under Assets for users that do not
      have download_code access.
      
      GET ':id/releases/:tag_name' still do not allow guests to access
      releases. This is to prevent guessing tag existence.
      241ba4be
  12. 09 4月, 2019 2 次提交
  13. 04 4月, 2019 1 次提交
  14. 14 3月, 2019 1 次提交
  15. 14 2月, 2019 1 次提交
  16. 13 2月, 2019 2 次提交
  17. 31 1月, 2019 2 次提交
  18. 19 12月, 2018 1 次提交
  19. 05 11月, 2018 1 次提交
  20. 05 10月, 2018 1 次提交
  21. 18 8月, 2018 1 次提交
  22. 23 7月, 2018 1 次提交
  23. 21 7月, 2018 1 次提交
  24. 18 6月, 2018 1 次提交
  25. 13 6月, 2018 2 次提交
  26. 12 6月, 2018 1 次提交
  27. 01 6月, 2018 1 次提交
  28. 29 5月, 2018 1 次提交
  29. 22 5月, 2018 1 次提交
  30. 01 5月, 2018 1 次提交
  31. 09 4月, 2018 1 次提交
    • A
      Expose the target commit ID through the tag API · 3a4086e2
      Andrew Beresford 提交于
      This is useful for annotated tags, where the deferenced target is not the same as the tag object. At the moment there is no way to differentiate the two through the tag API.
      
      This change adds a "target" property and leaves the existing "commit" property alone so that existing behaviour is not altered.
      3a4086e2
  32. 30 3月, 2018 1 次提交
  33. 07 3月, 2018 2 次提交
  34. 01 3月, 2018 1 次提交