- 29 5月, 2018 4 次提交
-
-
由 Jan Provaznik 提交于
`nil` value is not included in `ActiveModel::Type::Boolean::FALSE_VALUES` which caused that in Rails 5 the boolean_accessor converted `nil` to `true` instead of `false`.
-
由 Andreas Brandl 提交于
Closes #35364.
-
由 blackst0ne 提交于
-
由 Rémy Coutable 提交于
Ensure ApplicationSetting#performance_bar_allowed_group_id is properly set when retrieved from cache Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 28 5月, 2018 1 次提交
-
-
由 Andreas Brandl 提交于
This was needed for a transition phase only. For details see #45389. Closes #45389.
-
- 25 5月, 2018 2 次提交
-
-
由 Stan Hu 提交于
When deleting associated records, Rails loads all associations into memory (https://github.com/rails/rails/issues/22510) before destroying them. This can cause a surge in memory and cause destruction of objects to fail due to idle in transaction database timeouts. This fix is inspired from https://github.com/thisismydesign to destroy `has_many` relationships in batches. Closes #44610
-
由 Oswaldo Ferreira 提交于
We request Gitaly in a N+1 manner to build discussion diffs. Once the diffs are from different revisions, it's hard to make a single request to the service in order to build the whole response. With this change we solve this problem and simplify a lot fetching this piece of info.
-
- 24 5月, 2018 2 次提交
-
-
由 Felipe Artur 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 23 5月, 2018 4 次提交
-
-
由 Jan Provaznik 提交于
This can occur when a note is added to a commit and then this commit is deleted.
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Olivier Gonzalez 提交于
-
- 22 5月, 2018 3 次提交
-
-
由 Imre Farkas 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Douwe Maan 提交于
-
- 21 5月, 2018 2 次提交
-
-
由 Andreas Brandl 提交于
Closes #32258.
-
由 Shinya Maeda 提交于
-
- 18 5月, 2018 8 次提交
-
-
由 Mayra Cabrera 提交于
It was using name, instead of username. Fixes documentation as well Closes #46454
-
由 Matija Čupić 提交于
This reverts commit 2ebafdfb
-
由 Kamil Trzciński 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Mark Chao 提交于
-
由 Jacopo 提交于
-
由 Harish Ved 提交于
-
- 17 5月, 2018 13 次提交
-
-
由 Yorick Peterse 提交于
When displaying the pipelines of a project we now preload the following data: 1. Authors of the commits that belong to these pipelines 2. The number of warnings per pipeline, which is used by Ci::Pipeline#has_warnings? == Commit Authors Previously this data was queried for every Commit separately, leading to 20 SQL queries being executed in the worst case. With an average of 3 to 5 milliseconds per SQL query this could result in 100 milliseconds being spent in _just_ getting Commit authors. To preload this data Commit#author now uses BatchLoader (through Commit#lazy_author), and a separate module Gitlab::Ci::Pipeline::Preloader is used to ensure all authors are loaded before they are used. == Number of warnings This changes Ci::Pipeline#has_warnings? so it supports preloading of the number of warnings per pipeline. This removes the need for executing a COUNT(*) query for every pipeline just to see if it has any warnings or not.
-
由 Matija Čupić 提交于
-
由 🙈 jacopo beschi 🙉 提交于
-
由 lulalala 提交于
Old behavior of creating TODO when “Merge When Pipeline Succeeds” service fails, is generalized to: Create a TODO whenever MR became unmergeable (and similar to notification, MR author and merge_user are both applicable)
-
由 lulalala 提交于
Display MR unmergeable reasons
-
由 lulalala 提交于
For notifying via todo or email.
-
由 lulalala 提交于
First, transitions between can_be_merged & cannot_be_merged are removed, as they are currently blocked in `check_if_can_be_merged`. `can_be_merge` always returns to `unchecked` first, before it can transition to `cannot_be_merged` (and vice versa). We want to avoid repeated notification triggered by repeated transition between `cannot_be_merged` & `unchecked`. So we added `cannot_be_merged_recheck` state, similar to `unchecked`, but as a mean to remember it’s from cannot_be_merged. See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18042/#note_65945407 Since `unchecked` and `cannot_be_merged_recheck` both mean “we are in the middle of checking if it is mergeable”, quite often we need to see if merge_status is in either one of them, so `check_state?` is added to achieve this.
-
由 Matija Čupić 提交于
-
由 Matija Čupić 提交于
This reverts commit 4e1bb1d1.
-
由 Matija Čupić 提交于
-
由 Matija Čupić 提交于
-
由 Matija Čupić 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 16 5月, 2018 1 次提交
-
-
由 Grzegorz Bizon 提交于
-