- 04 4月, 2017 1 次提交
-
-
- 30 3月, 2017 1 次提交
-
-
由 Kim "BKC" Carlbäcker 提交于
- Migration in Repository#is_ancestor?
-
- 08 3月, 2017 2 次提交
-
-
由 Oswaldo Ferreira 提交于
-
由 Jordan Ryan Reuter 提交于
`Kaminari.paginate_array` takes some options, most relevant of which is a `total_count` parameter. Using the `commit_count` for `total_count` lets us correctly treat the return of `Repository#commits` as a subset of all the commits we may wish to list. Addition of a new `Repository#commit_count_for_ref` method was necessarry to allow the user to start from an arbitrary ref. Ref #1381
-
- 03 3月, 2017 3 次提交
-
-
由 Alejandro Rodríguez 提交于
This will be necessary when adding gitaly settings. This version doesn't make any functional changes, but allows us to include this breaking change in 9.0 and add the needed extra settings in the future with backwards compatibility
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 02 3月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 25 2月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 24 2月, 2017 5 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Rémy Coutable 提交于
This hack is needed because of an issue when --follow and --skip are passed to git log at the same time. See https://gitlab.com/gitlab-org/gitlab-ce/issues/23062Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 23 2月, 2017 5 次提交
-
-
由 Douwe Maan 提交于
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 14 2月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 07 2月, 2017 5 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 03 2月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
Backport changes from the EE-only squash implementation, which would otherwise conflict when merge CE into EE. <https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1024>
-
- 27 1月, 2017 1 次提交
-
-
由 Stan Hu 提交于
In repositories such as https://github.com/git/git.git, annotated tags can point to blobs, not necessarily to commits. `Repository` attempts to return the tags in the order of the commit date, but if a commit is not available the previous implementation would error due to a `nil` target. This change modifies the code to use the current time if a commit is not associated with the given tag. Closes #27228
-
- 26 1月, 2017 1 次提交
-
- 16 1月, 2017 1 次提交
-
-
由 Minqi Pan 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 06 1月, 2017 2 次提交
-
-
由 Lin Jen-Shin 提交于
-
由 Lin Jen-Shin 提交于
-
- 05 1月, 2017 3 次提交
-
-
由 Lin Jen-Shin 提交于
-
由 Lin Jen-Shin 提交于
We merge repository checks inside it so we don't have to check it on the call site, and we could also load the commit for the caller. This greatly reduce code duplication. Feedback: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7237#note_20572919
-
由 Lin Jen-Shin 提交于
-
- 20 12月, 2016 3 次提交
-
-
由 Hiroyuki Sato 提交于
-
由 Hiroyuki Sato 提交于
-
由 Hiroyuki Sato 提交于
-
- 14 12月, 2016 1 次提交
- 12 12月, 2016 1 次提交
-
-
由 Lin Jen-Shin 提交于
It's very weird that source_commit.raw_commit and rugged.branches[merge_request.target_branch].target should be completely the same. I checked with == and other values which proved that both should be the same, but still tests cannot pass for: spec/services/merge_requests/refresh_service_spec.rb I decided to give it up. We could just use SHA and that works fine anyway.
-
- 10 12月, 2016 1 次提交
-
-
由 Lin Jen-Shin 提交于
-