BigW Consortium Gitlab

  1. 03 Mar, 2017 1 commit
  2. 23 Feb, 2017 1 commit
  3. 03 Feb, 2017 1 commit
  4. 18 Nov, 2016 1 commit
    • Fix faulty deployment refs · f20eadcb
      Z.J. van de Weg authored
      In the 8.13 RC cycle, so before the release, there was a time in which
      references in git where stored by id instead of iid. This could be fixed
      by time, if the iid catches up with the id, it overwrites it. But in the
      mean time we have wrong refs in the folder.
      
      This commit fixes that. For all projects we have deployments we'll find
      the ones where the ref has a higher number than the iid is now and calls
      `#create_ref` on the corresponding deployment.
  5. 30 Jun, 2016 1 commit
  6. 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
  7. 15 Sep, 2015 2 commits
  8. 23 Jun, 2015 1 commit
  9. 09 Jun, 2015 1 commit
  10. 16 Feb, 2015 1 commit
  11. 12 Nov, 2014 1 commit
    • fixes the `block_removed_ldap_users` rake task · 1f902c24
      Marvin Frick authored
      In e23a26a (and later 1bc9936) the API for Gitlab::LDAP::Adapter was
      changed. I assume this rake task was an oversight in the refactoring of
      the changed class.
      
      While being on it, I noticed that already blocked users cannot be
      blocked again.
  12. 26 Jun, 2014 1 commit
  13. 29 Jul, 2013 1 commit
  14. 05 May, 2013 1 commit
  15. 11 Feb, 2013 1 commit
  16. 09 Feb, 2013 1 commit
  17. 25 Dec, 2012 1 commit