1. 06 4月, 2017 3 次提交
  2. 04 4月, 2017 2 次提交
  3. 22 3月, 2017 1 次提交
  4. 21 3月, 2017 1 次提交
  5. 20 3月, 2017 1 次提交
  6. 15 3月, 2017 1 次提交
  7. 02 3月, 2017 1 次提交
  8. 01 3月, 2017 1 次提交
    • J
      Update occurrences of MWBS to MWPS · a0101ebf
      James Lopez 提交于
       Rename column in the database
       Rename fields related to import/export feature
       Rename API endpoints
       Rename documentation links
       Rename the rest of occurrences in the code
       Replace the images that contain the words "build succeeds" and docs referencing to them
       Make sure pipeline is green and nothing is missing.
      
      updated doc images
      
      renamed only_allow_merge_if_build_succeeds in projects and fixed references
      
      more updates
      
      fix some spec failures
      
      fix rubocop offences
      
      fix v3 api spec
      
      fix MR  specs
      
      fixed issues with partials
      
      fix MR spec
      
      fix alignment
      
      add missing v3 to v4 doc
      
      wip - refactor v3 endpoints
      
      fix specs
      
      fix a few typos
      
      fix project specs
      
      copy entities fully to V3
      
      fix  entity error
      
      more fixes
      
      fix failing specs
      
      fixed missing entities in V3 API
      
      remove comment
      
      updated code based on feedback
      
      typo
      
      fix spec
      a0101ebf
  9. 25 2月, 2017 1 次提交
    • S
      Only create unmergeable todos once · 2da8bc3d
      Sean McGivern 提交于
      Previously, we created an unmergeable todo when a merge request:
      
      1. Had merge when pipeline succeeds set.
      2. Became unmergeable.
      
      However, when merge when pipeline succeeds fails due to unmergeability,
      the flag isn't actually removed. And a merge request can become
      unmergeable multiple times, as every time the target branch is updated
      we need to re-check the mergeable status. This means that if the todo
      was marked done, and the MR was checked again, a new todo would be
      created for the same event.
      
      Instead of checking this, we should create the todo from the service
      responsible for merging when the pipeline succeeds. That way the todo is
      guaranteed to only be created when we care about it.
      2da8bc3d
  10. 23 2月, 2017 6 次提交
  11. 15 2月, 2017 1 次提交
  12. 13 2月, 2017 1 次提交
  13. 07 2月, 2017 3 次提交
  14. 31 1月, 2017 1 次提交
  15. 28 1月, 2017 2 次提交
  16. 18 1月, 2017 1 次提交
  17. 14 1月, 2017 1 次提交
  18. 11 1月, 2017 1 次提交
  19. 04 1月, 2017 1 次提交
  20. 03 1月, 2017 1 次提交
  21. 30 12月, 2016 1 次提交
  22. 28 12月, 2016 1 次提交
  23. 26 12月, 2016 1 次提交
    • S
      Use raw_diffs to calculate MR files changed · ed6900ca
      Sean McGivern 提交于
      We don't need to create the intermediate FileCollection object with its
      associated highlighting in order to count how many files changed. Both
      the compare object and the MR diff object have a raw_diffs method that
      is perfectly fine for this case.
      ed6900ca
  24. 19 12月, 2016 1 次提交
  25. 16 12月, 2016 5 次提交