- 19 9月, 2017 5 次提交
-
-
由 Andrew Newdigate 提交于
-
由 Jedidiah 提交于
-
由 Eric Eastwood 提交于
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/33287 The MR widget was trying to render the pipelines section when there are no GitLab CI pipelines which was throwing some NPE errors.
-
由 Felipe Artur 提交于
-
由 haseeb 提交于
-
- 18 9月, 2017 8 次提交
-
-
由 Stan Hu 提交于
In #37955,we see that the profile had a number of N+1 queries from repeated access to `cross_reference_not_visible_for?`. This was optimized in previous versions of GitLab by rendering all notes at once, counting the number of visible references, and then using that number to check whether a system note should be fully redacted. There was also another N+1 query calling `ProjectTeam#member?`, which did not take advantage of an optimization in prepare_notes_for_rendering that would preload the maximum access level per project. Closes #37955
-
由 Robin Bobbitt 提交于
Closes #37789
-
由 winh 提交于
-
由 Pedro Moreira da Silva 提交于
Explain what a project is instead of what a user can do
-
由 Zeger-Jan van de Weg 提交于
When a user selected 'Instance default' as value for the auto devops settings, this was interpreted as a true value. Now we post an empty string in this case, meaning we want to set `NULL` in the database. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37893#note_40541294
-
由 Robert Schilling 提交于
-
由 Annabel Dunstone Gray 提交于
-
由 kushalpandya 提交于
-
- 17 9月, 2017 1 次提交
-
-
由 Phil Hughes 提交于
-
- 16 9月, 2017 2 次提交
-
-
由 Filipa Lacerda 提交于
-
由 Tiago Botelho 提交于
-
- 15 9月, 2017 11 次提交
-
-
由 Yorick Peterse 提交于
Prior to this commit running Namespace#force_share_with_group_lock_on_descendants would result in updating _all_ namespaces in the namespaces table, not just the descendants. This is the result of ActiveRecord::Relation#update_all not taking into account the CTE. To work around this we use the CTE query as a sub-query instead of directly calling #update_all. To prevent this from happening the relations returned by Gitlab::GroupHierarchy are now marked as read-only, resulting in an error being raised when methods such as #update_all are used. Fortunately on GitLab.com our statement timeouts appear to have prevented this query from actually doing any damage other than causing a very large amount of dead tuples. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37916
-
由 haseeb 提交于
-
由 Jacob Vosmaer 提交于
-
由 Winnie Hellmann 提交于
-
由 Rémy Coutable 提交于
* Improve the descriptive text * Rename "from" to "Target" and "to" to "Source" * Swap "Target" and "Source" to have the same order as in MRs * Reworded "Switch base of comparison" to "Swap versions" Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Phil Hughes 提交于
Closes #33124
-
由 Zeger-Jan van de Weg 提交于
Updating didn't work, as the project_id was missing to be set for the project_auto_devops model. Fixes gitlab-org/gitlab-ce#37893
-
由 Fabio Busatto 提交于
-
由 Jedidiah 提交于
-
由 Fatih Acet 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 14 9月, 2017 13 次提交
-
-
由 Jacob Vosmaer 提交于
-
由 Annabel Dunstone Gray 提交于
-
由 Yorick Peterse 提交于
This ensures that if a pipeline is present for the last commit on a project's homepage we only run 1 query to get the builds, instead of running 2 queries. See https://gitlab.com/gitlab-org/gitlab-ce/issues/36878#note_40073339 for more information.
-
由 Yorick Peterse 提交于
This adds Project#latest_successful_pipeline_for and Project#latest_successful_pipeline_for_default_branch. The 2nd method memoizes the result (taking nil values into account) to ensure the underlying query isn't executed multiple times when viewing a project's homepage. See https://gitlab.com/gitlab-org/gitlab-ce/issues/36878#note_40073607 for more information.
-
由 Jarka Kadlecova 提交于
This method was moved to ::Git but it is not cached there which causes performance problems
-
由 Dimitrie Hoekstra 提交于
-
由 Annabel Dunstone Gray 提交于
-
由 Annabel Dunstone Gray 提交于
-
由 Fatih Acet 提交于
-
由 Phil Hughes 提交于
Closes #37745
-
由 Fatih Acet 提交于
-
由 Fatih Acet 提交于
-
-