Re-enable ref operations with gitaly after not-found fix
What does this MR do?
Re-enable ref operations with gitaly after "repository not found" fix gitaly!120 (merged)
Are there points in the code the reviewer needs to double check?
No
Why was this MR needed?
These operations were already migrated to gitaly, but the incorrect handling of not found repositories forced us to disable it. We can reenable it now that it's been fixed.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
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