Skip to content

Prevent mirror service from calling Gitaly too much

Jacob Vosmaer (GitLab) requested to merge commits-are-ancestors into master

What does this MR do?

Add a new Gitlab::Git method to allow UpdateRemoteMirrorService to bypass Gitaly.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

UpdateRemoteMirrorService was calling Gitaly's CommitIsAncestor RPC too often. By letting this class bypass Gitaly we unblock the delivery of the CommitIsAncestor RPC. At a future stage we can migrate UpdateRemoteMirrorService#execute to Gitaly in its entirety using gitaly-ruby.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Closes https://gitlab.com/gitlab-org/gitaly/issues/418

Merge request reports