An error occurred fetching the project authors.
  1. 20 Nov, 2019 1 commit
  2. 15 Nov, 2019 1 commit
  3. 08 Jan, 2019 1 commit
  4. 22 Oct, 2018 1 commit
  5. 26 Jan, 2018 1 commit
  6. 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
  7. 01 Dec, 2017 1 commit
  8. 11 Aug, 2017 1 commit
  9. 03 Mar, 2017 1 commit
  10. 23 Feb, 2017 2 commits
  11. 03 Jun, 2016 1 commit
    • Connor Shea's avatar
      Replace colorize gem with rainbow. · 903946c7
      Connor Shea authored
      Colorize is a gem licensed under the GPLv2, so we can’t use it in GitLab without relicensing GitLab under the terms of the GPL. Rainbow is licensed under the MIT license and does the exact same thing as Colorize, so Rainbow was added in place of Colorize.
      
      The syntax is slightly different for Rainbow vs. Colorize, and was updated in accordance.
      
      The gem is still a dependency of Spinach, so it’s included in the development/test environments, but won’t be packaged with the actual product, and therefore doesn’t require we relicense the product.
      
      An attempt at relicensing Colorize was made, but didn’t succeed as the library owner never responded.
      
      Rainbow library: https://github.com/sickill/rainbow
      Relevant issue regarding licensing in GitLab's gems: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3775
      903946c7
  12. 26 Nov, 2015 1 commit
  13. 10 Nov, 2014 1 commit
  14. 26 Oct, 2014 1 commit
  15. 10 Jun, 2014 1 commit
  16. 15 Mar, 2014 1 commit
  17. 13 Nov, 2012 1 commit