- 25 Oct, 2017 1 commit
-
-
Francisco Lopez authored
Closes #25142
-
- 31 Aug, 2017 1 commit
-
-
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.
-
- 09 Jun, 2017 1 commit
-
-
Toon Claes authored
For quicker access, add hyperlink to the gitlab.com commits page for the current REVISION of GitLab.
-
- 23 Sep, 2015 3 commits
-
-
Robert Speicher authored
We want users to know what features they have available (and to pressure their admins to upgrade).
-
Robert Speicher authored
-
Robert Speicher authored
-