1. 29 7月, 2018 1 次提交
  2. 11 7月, 2018 1 次提交
  3. 09 7月, 2018 1 次提交
  4. 08 7月, 2018 1 次提交
  5. 05 6月, 2018 1 次提交
  6. 31 5月, 2018 3 次提交
  7. 22 5月, 2018 1 次提交
  8. 17 5月, 2018 1 次提交
  9. 16 5月, 2018 3 次提交
    • D
      c3f9d80a
    • D
      Allow group runners to be viewed/edited in API · 846f73b5
      Dylan Griffith 提交于
      846f73b5
    • J
      Delete remote uploads · 7da3b2cd
      Jan Provaznik 提交于
      ObjectStore uploader requires presence of associated `uploads` record
      when deleting the upload file (through the carrierwave's after_commit
      hook) because we keep info whether file is LOCAL or REMOTE in `upload`
      object.
      
      For this reason we can not destroy uploads as "dependent: :destroy" hook
      because these would be deleted too soon. Instead we rely on
      carrierwave's hook to destroy `uploads` in after_commit hook.
      
      But in before_destroy hook we still have to delete not-mounted uploads
      (which don't use carrierwave's destroy hook). This has to be done in
      before_Destroy instead of after_commit because `FileUpload` requires
      existence of model's object on destroy action.
      
      This is not ideal state of things, in a next step we should investigate
      how to unify model dependencies so we can use same workflow for all
      uploads.
      
      Related to #45425
      7da3b2cd
  10. 15 5月, 2018 1 次提交
  11. 10 5月, 2018 1 次提交
  12. 30 4月, 2018 1 次提交
  13. 26 4月, 2018 1 次提交
  14. 23 4月, 2018 2 次提交
  15. 09 4月, 2018 1 次提交
  16. 06 4月, 2018 1 次提交
  17. 05 4月, 2018 1 次提交
  18. 04 4月, 2018 1 次提交
  19. 29 3月, 2018 1 次提交
  20. 28 3月, 2018 1 次提交
    • B
      Remove permanent redirects · ce69419a
      Bob Van Landuyt 提交于
      Removes permanent redirects, this means that redirects will only be
      possible as long as the old route isn't taken by a new project/group.
      ce69419a
  21. 23 3月, 2018 1 次提交
  22. 07 3月, 2018 1 次提交
  23. 03 3月, 2018 1 次提交
  24. 18 2月, 2018 1 次提交
  25. 13 2月, 2018 1 次提交
    • P
      Strip whitespace from username/login value for user lookup · eddf4c0f
      Peter Lauck 提交于
      As per the discussion with @psimyn, this change does not affect the frontend, so user input will not be validated on the signin screen.
      
      Instead, the value sent to the backend has leading and trailing whitespace stripped before looking up the user with find_by.
      
      Closes #42637
      eddf4c0f
  26. 08 2月, 2018 1 次提交
  27. 07 2月, 2018 3 次提交
  28. 06 2月, 2018 2 次提交
  29. 05 2月, 2018 1 次提交
  30. 03 2月, 2018 1 次提交
  31. 25 1月, 2018 1 次提交
  32. 22 1月, 2018 1 次提交