Use gitaly commit is ancestor
Conversation: gitaly#221
What does this MR do?
Make it possible for GitLab to utilize Gitaly for commit-is-ancestor checks
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Based on and forked from !9629 (merged) since we use shared code