1. 29 4月, 2017 1 次提交
  2. 27 4月, 2017 1 次提交
  3. 01 3月, 2017 1 次提交
  4. 23 2月, 2017 2 次提交
  5. 22 2月, 2017 1 次提交
  6. 17 2月, 2017 1 次提交
  7. 19 1月, 2017 1 次提交
    • R
      Add some API endpoints for time tracking. · 0f3c9355
      Ruben Davila 提交于
      New endpoints are:
      
      POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_estimate"
      
      POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_time_estimate"
      
      POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/add_spent_time"
      
      POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_spent_time"
      
      GET  :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_stats"
      0f3c9355
  8. 16 1月, 2017 1 次提交
  9. 28 12月, 2016 1 次提交
  10. 16 12月, 2016 1 次提交
  11. 06 12月, 2016 1 次提交
    • B
      Feature: delegate all open discussions to Issue · 1123057a
      Bob Van Landuyt 提交于
      When a merge request can only be merged when all discussions are
      resolved. This feature allows to easily delegate those discussions to a
      new issue, while marking them as resolved in the merge request.
      
      The user is presented with a new issue, prepared with mentions of all
      unresolved discussions, including the first unresolved note of the
      discussion, time and link to the note.
      
      When the issue is created, the discussions in the merge request will get
      a system note directing the user to the newly created issue.
      1123057a
  12. 29 11月, 2016 1 次提交
  13. 23 11月, 2016 1 次提交
    • Y
      Remove event caching code · 5371da34
      Yorick Peterse 提交于
      Flushing the events cache worked by updating a recent number of rows in
      the "events" table. This has the result that on PostgreSQL a lot of dead
      tuples are produced on a regular basis. This in turn means that
      PostgreSQL will spend considerable amounts of time vacuuming this table.
      This in turn can lead to an increase of database load.
      
      For GitLab.com we measured the impact of not using events caching and
      found no measurable increase in response timings. Meanwhile not flushing
      the events cache lead to the "events" table having no more dead tuples
      as now rows are only inserted into this table.
      
      As a result of this we are hereby removing events caching as it does not
      appear to help and only increases database load.
      
      For more information see the following comment:
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037
      5371da34
  14. 18 11月, 2016 1 次提交
  15. 20 10月, 2016 4 次提交
  16. 28 9月, 2016 1 次提交
  17. 21 9月, 2016 1 次提交
  18. 31 8月, 2016 2 次提交
  19. 19 8月, 2016 1 次提交
  20. 18 8月, 2016 2 次提交
  21. 13 8月, 2016 7 次提交
  22. 15 7月, 2016 1 次提交
  23. 04 6月, 2016 3 次提交
  24. 19 5月, 2016 1 次提交
  25. 18 5月, 2016 1 次提交
  26. 22 4月, 2016 1 次提交