- 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.
-
- 30 Aug, 2017 1 commit
-
-
Douwe Maan authored
-
- 28 Aug, 2017 1 commit
-
-
Yorick Peterse authored
This ensures the project of an MR's head pipeline is eager loaded, preventing an N+1 query problem from occurring when viewing the list of MRs of a project.
-
- 18 Aug, 2017 1 commit
-
-
Douwe Maan authored
-
- 17 Aug, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 14 Aug, 2017 1 commit
-
-
Robert Speicher authored
An upcoming update to rubocop-gitlab-security added additional violations.
-
- 11 Aug, 2017 2 commits
-
-
Mehdi Lahmam authored
-
Douwe Maan authored
-
- 07 Aug, 2017 1 commit
-
-
Sean McGivern authored
-
- 03 Aug, 2017 2 commits
-
-
Filipa Lacerda authored
-
Douwe Maan authored
-
- 02 Aug, 2017 1 commit
-
-
Filipa Lacerda authored
-
- 29 Jul, 2017 2 commits
-
-
Jacob Schatz authored
-
Jacob Schatz authored
-
- 28 Jul, 2017 1 commit
-
-
Sean McGivern authored
A commit comment shows in the MR, but if the MR is from a fork, it will have a different project ID to the MR's target project. In that case, add an note_project_id param so that we can pick the correct project for the note.
-
- 21 Jul, 2017 1 commit
-
-
Douwe Maan authored
-
- 20 Jul, 2017 1 commit
-
-
Alexander Randa authored
-
- 19 Jul, 2017 1 commit
-
-
Sean McGivern authored
We were including controller params in the cache key, so the key for the header didn't match the one for the list itself!
-
- 10 Jul, 2017 1 commit
-
-
Jacob Schatz authored
-
- 09 Jul, 2017 1 commit
-
-
Stan Hu authored
Closes #34159
-
- 07 Jul, 2017 1 commit
-
-
Tim Zallmann authored
-
- 06 Jul, 2017 5 commits
-
-
Sean McGivern authored
This is an ID-less table with just three columns: an association to the merge request diff the commit belongs to, the relative order of the commit within the merge request diff, and the commit SHA itself. Previously we stored much more information about the commits, so that we could display them even when they were deleted from the repo. Since 8.0, we ensure that those commits are kept around for as long as the target repo itself is, so we don't need to duplicate that data in the database.
-
Pawel Chojnacki authored
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
A `performance_team` Flipper group has been created. By default this group is nil but this can be customized in `gitlab.yml` via the performance_bar.allowed_group setting. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 05 Jul, 2017 1 commit
-
-
Douwe Maan authored
-
- 04 Jul, 2017 4 commits
-
-
Pawel Chojnacki authored
-
Pawel Chojnacki authored
-
Pawel Chojnacki authored
-
Pawel Chojnacki authored
in favor of whitelist that will be used to control the access to monitoring resources
-
- 02 Jul, 2017 1 commit
-
-
Jacob Schatz authored
-
- 01 Jul, 2017 1 commit
-
-
Jacob Schatz authored
-
- 28 Jun, 2017 1 commit
-
-
Douwe Maan authored
-
- 21 Jun, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 20 Jun, 2017 1 commit
-
-
Jacob Schatz authored
-
- 16 Jun, 2017 2 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
- 15 Jun, 2017 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-