1. 09 Apr, 2018 1 commit
  2. 08 Apr, 2018 1 commit
  3. 05 Apr, 2018 2 commits
  4. 04 Apr, 2018 2 commits
  5. 03 Apr, 2018 2 commits
  6. 02 Apr, 2018 1 commit
  7. 30 Mar, 2018 1 commit
  8. 22 Mar, 2018 1 commit
  9. 16 Mar, 2018 1 commit
  10. 06 Mar, 2018 2 commits
  11. 02 Mar, 2018 1 commit
  12. 01 Mar, 2018 1 commit
  13. 21 Feb, 2018 2 commits
  14. 01 Feb, 2018 2 commits
  15. 31 Jan, 2018 1 commit
  16. 26 Jan, 2018 1 commit
  17. 25 Jan, 2018 2 commits
  18. 24 Jan, 2018 1 commit
  19. 23 Jan, 2018 1 commit
  20. 19 Jan, 2018 1 commit
  21. 11 Jan, 2018 1 commit
  22. 10 Jan, 2018 2 commits
  23. 09 Jan, 2018 2 commits
  24. 04 Jan, 2018 2 commits
  25. 02 Jan, 2018 1 commit
    • Stan Hu's avatar
      Fix `rake db:seed_fu` not doing anything in CI · ad88e3f8
      Stan Hu authored
      The default behavior of seed_fu is to load the fixtures using the RAILS_ENV
      environment.  In CI, since we set RAILS_ENV=test, nothing is ever
      loaded. Instead of `rake db:seed_fu`, use `rake gitlab:setup`, which sets up
      MySQL properly with limits.
      
      Closes #41517
      ad88e3f8
  26. 23 Dec, 2017 1 commit
  27. 22 Dec, 2017 1 commit
  28. 21 Dec, 2017 1 commit
  29. 19 Dec, 2017 1 commit
  30. 18 Dec, 2017 1 commit