An error occurred fetching the project authors.
- 03 Dec, 2019 1 commit
-
-
GitLab Bot authored
-
- 25 Nov, 2019 2 commits
-
-
Nick Thomas authored
-
GitLab Bot authored
-
- 20 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 19 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 05 Nov, 2019 1 commit
-
-
GitLab Bot authored
-
- 21 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 09 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 02 Oct, 2019 1 commit
-
-
GitLab Bot authored
-
- 30 Sep, 2019 1 commit
-
-
Paul Okstad authored
-
- 26 Sep, 2019 1 commit
-
-
Paul Okstad authored
-
- 19 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 18 Sep, 2019 1 commit
-
-
GitLab Bot authored
-
- 09 Sep, 2019 1 commit
-
-
GitalyBot authored
-
- 26 Aug, 2019 1 commit
-
-
Jacob Vosmaer authored
-
- 21 Aug, 2019 1 commit
-
-
Felipe Artur authored
-
- 13 Aug, 2019 1 commit
-
-
GitalyBot authored
-
- 12 Aug, 2019 1 commit
-
-
Jacob Vosmaer authored
-
- 07 Aug, 2019 1 commit
-
-
GitalyBot authored
-
- 01 Aug, 2019 1 commit
-
-
Paul Okstad authored
-
- 11 Jul, 2019 1 commit
-
-
GitalyBot authored
-
- 10 Jul, 2019 1 commit
-
-
GitalyBot authored
-
- 04 Jul, 2019 1 commit
-
-
GitalyBot authored
-
- 25 Jun, 2019 1 commit
-
-
GitalyBot authored
The setup was wrong, and due to Gitaly being a bit more strict it had to match up. The test is now accurate and passing again.
-
- 24 Jun, 2019 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 20 Jun, 2019 1 commit
-
-
Oswaldo Ferreira authored
This couples the code that transitions the `MergeRequest#merge_status` and refs/merge-requests/:iid/merge ref update. In general, instead of directly telling `MergeToRefService` to update the merge ref, we should rely on `MergeabilityCheckService` to keep both the merge status and merge ref synced. Now, if the merge_status is `can_be_merged` it means the merge-ref is also updated to the latest. We've also updated the logic to be more systematic and less user-based.
-
- 18 Jun, 2019 1 commit
-
-
GitalyBot authored
-
- 05 Jun, 2019 1 commit
-
-
Patrick Bajao authored
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13460
-
- 04 Jun, 2019 1 commit
-
-
Patrick Bajao authored
-
- 03 Jun, 2019 1 commit
-
-
Douwe Maan authored
This change makes sure Gitaly includes a fix to make rebase work again properly. Part of: https://gitlab.com/gitlab-org/gitlab-ce/issues/62353
-
- 30 May, 2019 1 commit
-
-
GitalyBot authored
-
- 20 May, 2019 1 commit
-
-
Paul Okstad authored
This version of Gitaly fixes a bug in gitaly-wrapper that prevented the proper detection of the executable path for a Gitaly process.
-
- 07 May, 2019 1 commit
-
-
GitalyBot authored
-
- 06 May, 2019 1 commit
-
-
Nick Thomas authored
-
- 02 May, 2019 1 commit
-
-
John Cai authored
Includes catfile cache, as well as fixes to the catfile cache code that caused it to panic in Gitaly
-
- 29 Apr, 2019 1 commit
-
-
GitalyBot authored
-
- 25 Apr, 2019 1 commit
-
-
John Cai authored
Updates the gitaly client to use path_bytes field instead of the deprecated path field in list_last_commits_for_tree_response. Also adds a test to guard against non-utf8 path data
-
- 18 Apr, 2019 1 commit
-
-
John Cai authored
-
- 05 Apr, 2019 2 commits