Re-enable gitaly migration for ref_name_for_sha after bugfixes
Conversation: gitaly#221 (closed)
What does this MR do?
Re-enable gitaly migration for ref_name_for_sha after bugfixes
Are there points in the code the reviewer needs to double check?
No
Why was this MR needed?
The migration had to be disabled because of gitaly#180 (closed), which has been fixed now.
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