- 09 8月, 2016 1 次提交
-
-
由 tiagonbotelho 提交于
-
- 04 8月, 2016 2 次提交
-
-
由 Paco Guzman 提交于
-
由 Douwe Maan 提交于
-
- 03 8月, 2016 2 次提交
-
-
由 Paco Guzman 提交于
So we have raw_diffs too
-
由 Paco Guzman 提交于
Instead calling diff_collection.count use diff_collection.size which is cache on the diff_collection
-
- 02 8月, 2016 1 次提交
-
-
由 Paco Guzman 提交于
Speedup DiffNote#active? on discussions, preloading noteables and avoid touching git repository to return diff_refs when possible - Preloading noteable we share the same noteable instance when more than one discussion refers to the same noteable. - Any other call to that object that is cached in that object will be for any discussion. - In those cases where merge_request_diff has all the sha stored to build a diff_refs get that diff_refs using directly those sha instead accessing to the git repository to first get the commits and later the sha.
-
- 01 8月, 2016 1 次提交
-
-
When importing a pull request from GitHub, the old and new branches may no longer actually exist by those names, but we need to recreate the merge request diff with the right source and target shas. We use these `target_branch_sha` and `source_branch_sha` attributes to force these to the intended values. But the reader methods were always looking up to the target/source branch head instead of check if these values was previously set.
-
- 08 7月, 2016 1 次提交
-
-
由 Sean McGivern 提交于
When rendering a list of diff files, skip those where the diff is over 10 KB and provide an endpoint to render individually instead.
-
- 07 7月, 2016 2 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 04 7月, 2016 1 次提交
-
-
由 Douwe Maan 提交于
-
- 10 6月, 2016 4 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
The logic of the method was obviously inverted. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Based on the feedback from reviewers. Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rui Anderson 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 03 6月, 2016 4 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
由 James Lopez 提交于
This reverts commit 3e991230.
-
由 James Lopez 提交于
# Conflicts: # app/models/project.rb
-
- 02 6月, 2016 2 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Josh Frye 提交于
-
- 01 6月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
There are several changes to this module: 1. The use of an explicit stack in Participable#participants 2. Proc behaviour has been changed 3. Batch permissions checking == Explicit Stack Participable#participants no longer uses recursion to process "self" and all child objects, instead it uses an Array and processes objects in breadth-first order. This allows us to for example create a single Gitlab::ReferenceExtractor instance and pass this to any Procs. Re-using a ReferenceExtractor removes the need for running potentially many SQL queries every time a Proc is called on a new object. == Proc Behaviour Changed Previously a Proc in Participable was expected to return an Array of User instances. This has been changed and instead it's now expected that a Proc modifies the Gitlab::ReferenceExtractor passed to it. The return value of the Proc is ignored. == Permissions Checking The method Participable#participants uses Ability.users_that_can_read_project to check if the returned users have access to the project of "self" _without_ running multiple SQL queries for every user.
-
- 30 5月, 2016 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 20 5月, 2016 1 次提交
-
-
由 Jeroen Jacobs 提交于
-
- 14 5月, 2016 1 次提交
-
-
- 10 5月, 2016 1 次提交
-
-
由 Jeroen van Baarsen 提交于
In 8278b763 the default behaviour of annotation has changes, which was causing a lot of noise in diffs. We decided in #17382 that it is better to get rid of the whole annotate gem, and instead let people look at schema.rb for the columns in a table. Fixes: #17382
-
- 12 4月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 29 3月, 2016 1 次提交
-
-
由 Abhi Rao 提交于
Fixes #14692
-
- 20 3月, 2016 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 19 3月, 2016 2 次提交
-
-
由 Rémy Coutable 提交于
-
由 Rémy Coutable 提交于
We have to ensure source_sha and target_sha are not nil before calling Gitlab::Git::Commit.between.
-
- 18 3月, 2016 1 次提交
-
-
- 16 3月, 2016 2 次提交
-
-
由 Pierre de La Morinerie 提交于
`MergeRequest#source_sha` is expected to return the sha of the source branch last commit. But when a open Merge Request has no diff (e.g. all commits have already been merged to the target branch), `merge_request.source_sha` incorrectly returns `nil`. This was un-noticed before – but now that !2217 has been merged, it makes `Gitlab::Git::Commit.between` raise an "Unexpected nil argument" exception. This fixes the crash, by making sure that `source_sha` returns a correct result even when there is no diff available.
-
由 Pierre de La Morinerie 提交于
-
- 12 3月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
The OR condition for source_project_id/target_project_id leads to a query plan that performs rather poorly on PostgreSQL due to the use of sub-queries. Because Rails offers no easy alternative for this particular problem we're forced to using a UNION for both conditions. The resulting query performs much faster than just using an OR.
-
- 03 3月, 2016 1 次提交
-
-
由 Pierre de La Morinerie 提交于
-
- 20 2月, 2016 1 次提交
-
-
由 Rubén Dávila 提交于
-
- 12 2月, 2016 1 次提交
-
-
由 Kirill Zaitsev 提交于
- Add `avatar_url`, `description`, `git_ssh_url`, `git_http_url`, `path_with_namespace` and `default_branch` in `project` in push, issue, merge-request and note webhooks data - Deprecate the `ssh_url` in favor of `git_ssh_url` and `http_url` in favor of `git_http_url` in `project` for push, issue, merge-request and note webhooks data - Deprecate the `repository` key in push, issue, merge-request and note webhooks data, use `project` instead
-
- 04 2月, 2016 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Fixes #3339 This MR hides the 'Remove source branch' button when a new commit is added to the source branch
-