Re-enable gitaly migration for ref_name_for_sha after bugfixes

Conversation: https://gitlab.com/gitlab-org/gitaly/issues/221

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 https://gitlab.com/gitlab-org/gitaly/issues/180, 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

What are the relevant issue numbers?

marked the checklist item API support added as completed

marked the checklist item API support added as incomplete

marked the checklist item Added for this feature/bug as completed

marked the checklist item Conform by the merge request performance guides as completed

marked the checklist item Conform by the style guides as completed

marked the checklist item Squashed related commits together as completed

approved this merge request

Other than the comment it LGTM :)

added 1 commit

• 6b5923d4 - Re-enable gitaly migration for ref_name_for_sha after bugfixes

Compare with previous version

assigned to @jacobvosmaer-gitlab

assigned to @eReGeBe

changed milestone to %9.2

added Gitaly label

mentioned in issue gitaly#210 (closed)

mentioned in issue gitaly#221

assigned to @rspeicher

@eReGeBe LGTM, please address Jacob's comment.

assigned to @eReGeBe

added 272 commits

• 6b5923d4...9a10a6bf - 271 commits from branch master
• cf09c826 - Re-enable gitaly migration for ref_name_for_sha after bugfixes

Compare with previous version

assigned to @rspeicher

@rspeicher regarding ee-compat-check, it seems that EE master is somewhat outdated: it has an older GITALY_SERVER_VERSION and GitalyClient code. The conflict is very straightforward to fix, can we resolve it on the CE Upstream merge?

resolved all discussions

approved this merge request

merged

mentioned in commit e66b811d

mentioned in issue #31934 (closed)

Picked into 9-2-stable will go into 9-2 RC6

mentioned in commit a72a3cc2

mentioned in issue gitaly#309 (closed)