BigW Consortium Gitlab

  1. 25 Jul, 2017 1 commit
  2. 16 Jun, 2017 1 commit
    • Add table for files in merge request diffs · 9a73b634
      Sean McGivern authored
      This adds an ID-less table containing one row per file, per merge request
      diff. It has a column for each attribute on Gitlab::Git::Diff that is serialised
      currently, with the advantage that we can easily query the attributes of this
      new table.
      
      It does not migrate existing data, so we have fallback code when the legacy
      st_diffs column is present instead. For a merge request diff to be valid, it
      should have at most one of:
      
      * Rows in this new table, with the correct merge_request_diff_id.
      * A non-NULL st_diffs column.
      
      It may have neither, if the diff is empty.
  3. 08 May, 2017 1 commit
  4. 05 May, 2017 1 commit
  5. 03 May, 2017 1 commit
  6. 21 Mar, 2017 1 commit
  7. 23 Feb, 2017 1 commit
  8. 13 Dec, 2016 1 commit
  9. 03 Jun, 2016 1 commit
    • 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
  10. 15 Oct, 2015 1 commit
    • Improve performance of User.by_login · 72f428c7
      Yorick Peterse authored
      Performance is improved in two steps:
      
      1. On PostgreSQL an expression index is used for checking lower(email)
         and lower(username).
      2. The check to determine if we're searching for a username or Email is
         moved to Ruby. Thanks to @haynes for suggesting and writing the
         initial implementation of this.
      
      Moving the check to Ruby makes this method an additional 1.5 times
      faster compared to doing the check in the SQL query.
      
      With performance being improved I've now also tweaked the amount of
      iterations required by the User.by_login benchmark. This method now runs
      between 900 and 1000 iterations per second.
  11. 08 Oct, 2015 1 commit
  12. 23 Jun, 2015 1 commit
  13. 23 Apr, 2014 1 commit
  14. 13 Mar, 2014 1 commit
  15. 12 Mar, 2014 1 commit
  16. 11 Mar, 2014 1 commit
  17. 26 Aug, 2013 1 commit
    • Remove old migration tasks · 3cc26654
      Dmitriy Zaporozhets authored
      You should update to 6.0 before proceed with update to higher version.
      So its no reason to keep old tasks any more.
      It should be still available in 6-0-stable but not in master
  18. 21 Aug, 2013 1 commit
  19. 20 Aug, 2013 2 commits
  20. 19 Aug, 2013 2 commits
  21. 04 Aug, 2013 2 commits
  22. 02 Aug, 2013 1 commit
  23. 29 Jul, 2013 1 commit
  24. 24 Jun, 2013 1 commit
  25. 22 Jun, 2013 1 commit
  26. 19 Jun, 2013 2 commits
  27. 11 May, 2013 1 commit
    • Migrate notes.line_code format. · 320f0ac8
      baba authored
      Since version 4.1, notes.line_code means:
        {SHA1 hash of file path}_{old line}_{new line}
      but the older version means:
        {file index of the commit}_{old line}_{new line}
      
      This rake task migrate the above differences.
  28. 16 Apr, 2013 1 commit
  29. 15 Apr, 2013 1 commit
  30. 10 Apr, 2013 1 commit
  31. 05 Apr, 2013 1 commit