Implement OperationService.UserAddBranch Gitaly RPC
What does this MR do?
Implement OperationService.UserAddBranch Gitaly RPC
Are there points in the code the reviewer needs to double check?
No
Why was this MR needed?
https://gitlab.com/gitlab-org/gitaly/issues/540
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together
What are the relevant issue numbers?
Merge request reports
Activity
assigned to @smcgivern
mentioned in issue gitaly#540
assigned to @eReGeBe
added 58 commits
- 2363e08d...05d8e87d - 55 commits from branch
master - 1b7e2f1e - Add a factory for
Gitaly::GitCommits - fa657b11 - Update to gitaly-proto 0.35.0 and add helpers for the new types
- 5b0cfdfc - Implement OperationService.UserAddBranch Gitaly RPC
Toggle commit list- 2363e08d...05d8e87d - 55 commits from branch
assigned to @smcgivern
@eReGeBe LGTM, thanks! Can you fix the conflicts, please?
assigned to @eReGeBe
added 203 commits
- 02b8efbb...aec1586c - 200 commits from branch
master - b53ded74 - Add a factory for
Gitaly::GitCommits - b7777ce2 - Add helpers for the new Gitaly types
- e81190f4 - Implement OperationService.UserAddBranch Gitaly RPC
Toggle commit list- 02b8efbb...aec1586c - 200 commits from branch
Tried cherry picking into EE because of the compat_check failures, it seems it's caused by https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14566 not being on EE master, so this should apply cleanly when the CE -> EE merge occurs.
assigned to @smcgivern
Thanks @eReGeBe!
mentioned in commit 0a69abdb
Please register or sign in to reply