1. 07 Mar, 2017 1 commit
  2. 06 Mar, 2017 1 commit
  3. 23 Feb, 2017 3 commits
  4. 06 Feb, 2017 1 commit
  5. 27 Jan, 2017 1 commit
  6. 23 Jan, 2017 1 commit
  7. 18 Jan, 2017 1 commit
    • Ruben Davila's avatar
      Add some API endpoints for time tracking. · 0f3c9355
      Ruben Davila authored
      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. 17 Jan, 2017 1 commit
  9. 13 Dec, 2016 1 commit
  10. 04 Dec, 2016 1 commit
  11. 30 Nov, 2016 1 commit
  12. 29 Nov, 2016 2 commits
  13. 28 Nov, 2016 1 commit
  14. 22 Nov, 2016 1 commit
  15. 21 Nov, 2016 1 commit
  16. 15 Nov, 2016 1 commit
  17. 01 Nov, 2016 1 commit
  18. 28 Sep, 2016 1 commit
    • Rémy Coutable's avatar
      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: default avatarRémy Coutable <remy@rymai.me>
      ec0061a9
  19. 31 Aug, 2016 1 commit
  20. 24 Aug, 2016 1 commit
  21. 09 Aug, 2016 1 commit
  22. 11 Jul, 2016 1 commit
  23. 07 Jul, 2016 1 commit
  24. 06 Jul, 2016 1 commit
  25. 27 Jun, 2016 1 commit
  26. 12 Jun, 2016 1 commit
  27. 10 Jun, 2016 3 commits
  28. 06 Jun, 2016 1 commit
  29. 03 Jun, 2016 3 commits
  30. 02 Jun, 2016 1 commit
  31. 01 Jun, 2016 1 commit
    • Sean McGivern's avatar
      Add `sha` parameter to MR accept API · d863d86a
      Sean McGivern authored
      The `sha` parameter is optional, and when present, must match the
      current HEAD SHA of the source branch. Otherwise, the API call fails
      with a 409 Conflict and a message containing the current HEAD for the
      source branch.
      
      Also tidy up some doc wording.
      d863d86a
  32. 11 May, 2016 1 commit
  33. 09 May, 2016 1 commit