1. 24 2月, 2017 1 次提交
  2. 22 2月, 2017 1 次提交
  3. 20 2月, 2017 1 次提交
  4. 16 2月, 2017 1 次提交
  5. 15 2月, 2017 2 次提交
  6. 27 1月, 2017 1 次提交
  7. 03 1月, 2017 1 次提交
  8. 14 12月, 2016 1 次提交
  9. 13 12月, 2016 2 次提交
  10. 01 12月, 2016 1 次提交
  11. 29 11月, 2016 1 次提交
  12. 24 10月, 2016 1 次提交
  13. 11 10月, 2016 1 次提交
  14. 06 10月, 2016 1 次提交
    • M
      multi-file commit · a1ee8cf5
      Marc Siegfriedt 提交于
      add docs and tests - add additional validation
      allow move without content
      updated response
      a1ee8cf5
  15. 19 9月, 2016 1 次提交
  16. 14 9月, 2016 1 次提交
  17. 12 9月, 2016 1 次提交
  18. 16 8月, 2016 1 次提交
  19. 11 8月, 2016 2 次提交
    • K
      Pre-create all builds for Pipeline when a trigger is received · 39203f1a
      Kamil Trzcinski 提交于
      This change simplifies a Pipeline processing by introducing a special new status: created.
      This status is used for all builds that are created for a pipeline.
      We are then processing next stages and queueing some of the builds (created -> pending) or skipping them (created -> skipped).
      This makes it possible to simplify and solve a few ordering problems with how previously builds were scheduled.
      This also allows us to visualise a full pipeline (with created builds).
      
      This also removes an after_touch used for updating a pipeline state parameters.
      Right now in various places we explicitly call a reload_status! on pipeline to force it to be updated and saved.
      39203f1a
    • L
      4b559c9a
  20. 09 8月, 2016 1 次提交
  21. 03 8月, 2016 1 次提交
  22. 28 7月, 2016 1 次提交
  23. 28 6月, 2016 1 次提交
  24. 03 6月, 2016 2 次提交
  25. 29 4月, 2016 1 次提交
  26. 17 4月, 2016 1 次提交
  27. 12 4月, 2016 1 次提交
  28. 07 3月, 2016 1 次提交
  29. 12 10月, 2015 1 次提交
  30. 08 5月, 2015 1 次提交
    • M
      Order commit comments in API chronologically · 55f91f3d
      Martin Luder 提交于
      When fetching commit comments via API, the comments were not ordered,
      but just returned in the order Postgresql finds them. Now the API always
      returns comments in chronological order.
      55f91f3d
  31. 13 2月, 2015 1 次提交
  32. 26 9月, 2014 1 次提交
  33. 15 9月, 2014 3 次提交
  34. 18 6月, 2014 1 次提交