Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-12-17 | Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42 | GitLab Bot | |
2019-03-06 | Adds the Rubocop ReturnNil cop | Andrew Newdigate | |
This style change enforces `return if ...` instead of `return nil if ...` to save maintainers a few minor review points | |||
2019-01-07 | Refactor upload service to return uploader | Heinrich Lee Yu | |
Also changes old calls to the service | |||
2019-01-07 | Import CSV Backend | Heinrich Lee Yu | |
Process CSV uploads async using a worker then email results | |||
2018-07-16 | Enable frozen string in apps/uploaders/*.rb | gfyoung | |
Partially addresses #47424. | |||
2018-07-11 | refactor uploads manager | James Lopez | |
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. | |||
2017-05-02 | Support uploaders for personal snippets comments | Jarka Kadlecova | |