- 30 Jan, 2018 4 commits
-
-
Ahmad Sherif authored
Fixes #42544
-
Jacob Vosmaer authored
-
Jacob Vosmaer (GitLab) authored
-
Kim "BKC" Carlbäcker authored
-
- 25 Jan, 2018 1 commit
-
-
Jacob Vosmaer authored
-
- 24 Jan, 2018 2 commits
-
-
Ahmad Sherif authored
Closes gitaly#946
-
Ahmad Sherif authored
Closes gitaly#929
-
- 22 Jan, 2018 1 commit
-
-
Kim "BKC" Carlbäcker authored
-
- 18 Jan, 2018 1 commit
-
-
Kim "BKC" Carlbäcker authored
-
- 16 Jan, 2018 2 commits
-
-
Sean McGivern authored
A file containing /:\d+:/ in its contents would break the search results if those contents were part of the results, because we were splitting on colons, which can't work with untrusted input. Changing to use the null byte as a separator is much safer.
-
Andrew McCallum authored
-
- 15 Jan, 2018 4 commits
-
-
Andrew McCallum authored
-
Andrew McCallum authored
-
Andrew McCallum authored
-
Andrew McCallum authored
-
- 12 Jan, 2018 1 commit
-
-
Lin Jen-Shin authored
with StrongMemoize
-
- 11 Jan, 2018 2 commits
-
-
🙈 jacopo beschi 🙉 authored
-
Ahmad Sherif authored
-
- 10 Jan, 2018 1 commit
-
-
Stan Hu authored
Closes #41739
-
- 09 Jan, 2018 1 commit
-
-
Kim "BKC" Carlbäcker authored
-
- 05 Jan, 2018 3 commits
-
-
Alejandro Rodríguez authored
-
Lin Jen-Shin (godfat) authored
-
Jan Provaznik authored
When a project uses fast-forward merging strategy user has to rebase MRs to target branch before it can be merged. Now user can do rebase in UI by clicking 'Rebase' button instead of doing rebase locally. This feature was already present in EE, this is only backport of the feature to CE. Couple of changes: * removed rebase license check * renamed migration (changed timestamp) Closes #40301
-
- 22 Dec, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 20 Dec, 2017 1 commit
-
-
Kim Carlbäcker authored
This reverts merge request !15712
-
- 19 Dec, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
Uses `list_commits_by_oid` on the CommitService, to request the needed commits for pipelines. These commits are needed to display the user that created the commit and the commit title. This includes fixes for tests failing that depended on the commit being `nil`. However, now these are batch loaded, this doesn't happen anymore and the commits are an instance of BatchLoader.
-
- 14 Dec, 2017 1 commit
-
-
haseeb authored
-
- 13 Dec, 2017 2 commits
-
-
Jacopo authored
Allows ordering in GET api/v4/projects/:project_id/repository/contributors through `order_by` and `sort` params. The available `order_by` options are: name|email|commits. The available `sort` options are: asc|desc.
-
Ahmad Sherif authored
Closes gitaly#808
-
- 12 Dec, 2017 2 commits
-
-
Stan Hu authored
-
Kim "BKC" Carlbäcker authored
-
- 07 Dec, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 06 Dec, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 01 Dec, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
This has the side effect of making this method rugged call free, which is the reason I actually changed this.
-
- 23 Nov, 2017 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Lin Jen-Shin authored
-
- 21 Nov, 2017 2 commits
-
-
Jacob Vosmaer (GitLab) authored
-
Zeger-Jan van de Weg authored
After installing a new gem, batch-loader, a construct can be used to queue data to be fetched in bulk. The gem was also introduced in both gitlab-org/gitlab-ce!14680 and gitlab-org/gitlab-ce!14846, but those mrs are not merged yet. For the generation of diffs, both the old blob and the new blob need to be loaded. This for every file in the diff, too. Now we collect all these so we do 1 fetch. Three `.allow_n_plus_1_calls` have been removed, which I expect to be valid, but this needs to be confirmed by a full CI run. Possibly closes: - https://gitlab.com/gitlab-org/gitlab-ce/issues/37445 - https://gitlab.com/gitlab-org/gitlab-ce/issues/37599 - https://gitlab.com/gitlab-org/gitlab-ce/issues/37431
-
- 17 Nov, 2017 1 commit
-
-
Sean McGivern authored
Conflicts used to take a `Repository` and pass that to `Gitlab::Highlight.highlight`, which would call `#gitattribute` on the repository. Now they use a `Gitlab::Git::Repository`, which didn't have that method defined - but defining it on `Gitlab::Git::Repository` does make it available on `Repository` through `method_missing`, so we can do that and both cases will work.
-