Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-06-20 | Add latest changes from gitlab-org/gitlab@15-1-stable-eev15.1.0-rc42 | GitLab Bot | |
2018-10-22 | Enable frozen string for lib/gitlab/*.rb | gfyoung | |
2018-02-02 | use Gitlab::UserSettings directly as a singleton instead of ↵ | Mario de la Ossa | |
including/extending it | |||
2017-08-31 | `current_application_settings` belongs on `Gitlab::CurrentSettings` | Sean McGivern | |
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. | |||
2016-07-06 | Default Git access protocol to `web` | Patricio Cano | |
2016-07-06 | Rename `enabled_git_access_protocols` to singular. | Patricio Cano | |
2016-07-06 | Clarify protocol access check, and make Git HTTP access call more specific. | Patricio Cano | |
2016-07-06 | Only allow Git Access on the allowed protocol | Patricio Cano | |