BigW Consortium Gitlab

  1. 03 Oct, 2017 1 commit
  2. 02 Oct, 2017 1 commit
  3. 28 Sep, 2017 1 commit
  4. 26 Sep, 2017 1 commit
  5. 22 Sep, 2017 2 commits
  6. 20 Sep, 2017 1 commit
  7. 18 Sep, 2017 1 commit
  8. 16 Sep, 2017 2 commits
  9. 14 Sep, 2017 4 commits
  10. 11 Sep, 2017 2 commits
  11. 08 Sep, 2017 1 commit
    • Revert "Merge branch… · 52a2423e
      Rubén Dávila authored
      Revert "Merge branch '35012-navigation-add-option-to-change-navigation-color-palette' into 'master'"
      
      This reverts merge request !13619
  12. 07 Sep, 2017 1 commit
  13. 06 Sep, 2017 3 commits
  14. 05 Sep, 2017 2 commits
  15. 03 Sep, 2017 2 commits
  16. 01 Sep, 2017 1 commit
  17. 31 Aug, 2017 1 commit
    • `current_application_settings` belongs on `Gitlab::CurrentSettings` · 5883ce95
      Sean McGivern authored
      The initializers including this were doing so at the top level, so every object
      loaded after them had a `current_application_settings` method. However, if
      someone had rack-attack enabled (which was loaded before these initializers), it
      would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
      have that method.
      
      To fix this:
      
      1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
         `Object.new.current_application_settings` to work.
      2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
         like that in several places.
      3. Change the initializers to use that new form.
  18. 30 Aug, 2017 2 commits
  19. 29 Aug, 2017 1 commit
  20. 28 Aug, 2017 6 commits
  21. 24 Aug, 2017 1 commit
  22. 23 Aug, 2017 2 commits
  23. 22 Aug, 2017 1 commit