Experimental remote branches via ls-remote
Currently, we return a list of remote branches by fetching the remote and then using Rugged to get heads from refs/remotes/<remote_name>/
. This is undesirable for the reasons outlined in #2670 (closed).
This merge request uses that branch list as a control, and then fetches a second list of remote branches via ls-remote
to compare the result. This is behind a gitaly-feature-ruby-remote-branches-ls-remote
feature flag.
As a first experimental step, any differences between these two branch lists is simply logged. After a testing period, we can change the behavior so that it only does one or the other, depending on the flag, before switching over entirely.
Related to #2670 (closed).
TODO
-
Enable a gitaly_ruby_remote_branches_ls_remote
flag (this gets translated togitaly-feature-ruby-remote-branches-ls-remote
).
Edited by GitLab Release Tools Bot