- 04 Apr, 2018 2 commits
-
-
Zeger-Jan van de Weg authored
Has been stable for a while in production, so this endpoint grew out if OPT_IN, the default state. Part of https://gitlab.com/gitlab-org/gitaly/issues/526
-
Zeger-Jan van de Weg authored
Acceptence testing was successfull in [#844](https://gitlab.com/gitlab-org/gitaly/issues/844) Part of gitlab-org/gitaly#670
-
- 03 Apr, 2018 2 commits
-
-
Douglas Barbosa Alexandre authored
-
Ahmad Sherif authored
Closes gitaly#1110
-
- 30 Mar, 2018 2 commits
-
-
Stan Hu authored
Any submodule lines that had a CR-LF ending would be ignored by the parser. Closes gitlab-org/gitlab-ce#2262
-
Jacob Vosmaer (GitLab) authored
-
- 27 Mar, 2018 1 commit
-
-
Douwe Maan authored
-
- 23 Mar, 2018 1 commit
-
-
Sean McGivern authored
When we added caching, this meant that calling `can_be_resolved_in_ui?` didn't always call `lines`, which meant that we didn't get the benefit of the side-effect from that, where it forced the conflict data itself to UTF-8. To fix that, make this explicit by separating the `raw_content` (any encoding) from the `content` (which is either UTF-8, or an exception is raised).
-
- 22 Mar, 2018 1 commit
-
-
Alejandro Rodríguez authored
Before we were using a "plumbing" Gitlab::Git method that does not go through Gitaly migration checking.
-
- 21 Mar, 2018 2 commits
-
-
Jacob Vosmaer authored
-
Ahmad Sherif authored
They were probably added to compensate for tests shortcomings, but now they don't complain. Closes gitaly#1095
-
- 19 Mar, 2018 1 commit
-
-
Jasper Maes authored
Split repository search result on \n instead of $ to prevent the items of the array to start with a newline. Remove the strip from parsing the search result to keep result endlines.
-
- 16 Mar, 2018 1 commit
-
-
James Edwards-Jones authored
-
- 15 Mar, 2018 2 commits
-
-
James Edwards-Jones authored
-
James Edwards-Jones authored
Prevents `.gitattributes` blob lookup being repeated for every file checked at a given ref
-
- 12 Mar, 2018 1 commit
-
-
Nick Thomas authored
-
- 08 Mar, 2018 2 commits
-
-
Kim "BKC" Carlbäcker authored
-
Jacob Vosmaer authored
-
- 07 Mar, 2018 9 commits
-
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#476
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#476
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitlab-ce!17561
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#540
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#546
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#779
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#541
-
Zeger-Jan van de Weg authored
Part of gitlab-org/gitaly#324
-
Zeger-Jan van de Weg authored
Part of gitlab-org/gitaly#616
-
- 06 Mar, 2018 3 commits
-
-
Ahmad Sherif authored
Fixes gitaly#1057 The old code was calling LastCommitForPath to extract a commit ID _then_ call FindCommit to get a commit it already had in the first place!
-
Takuya Noguchi authored
-
Stan Hu authored
By default, --prune is added to the command-line of a `git fetch` operation, but for repositories with many references this can take a long time to run. We shouldn't need to run --prune the first time we fetch a new repository.
-
- 05 Mar, 2018 1 commit
-
-
Alejandro Rodríguez authored
-
- 02 Mar, 2018 2 commits
-
-
Alejandro Rodríguez authored
-
Ahmad Sherif authored
-
- 01 Mar, 2018 3 commits
-
-
Ahmad Sherif authored
Closes gitaly#1046
-
Zeger-Jan van de Weg authored
Part of the migration as tracked in: gitlab-org/gitaly#1026
-
Tiago Botelho authored
-
- 28 Feb, 2018 1 commit
-
-
Kim Carlbäcker authored
-
- 26 Feb, 2018 2 commits
-
-
Ahmad Sherif authored
-
Sean McGivern authored
These are obscuring the real error, which is confusing for everyone.
-
- 23 Feb, 2018 1 commit
-
-
Tiago Botelho authored
-