BigW Consortium Gitlab
When a repository does not exist on a remote, Gitaly won't be able to clone it. This is correct behaviour, but from the clients perspective a change in behaviour. This change implements the client side changes that allows Gitaly to execute a `git ls-remote <remote-url> HEAD`. This way the client has no need to shell out to Git. In the situation where multiple Gitalies are available, one is chosen at random. This commit closes https://gitlab.com/gitlab-org/gitlab-ce/issues/43929, while its also a part of https://gitlab.com/gitlab-org/gitaly/issues/1084
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
blob_service_spec.rb | Loading commit data... | |
blobs_stitcher_spec.rb | Loading commit data... | |
commit_service_spec.rb | Loading commit data... | |
conflict_files_stitcher_spec.rb | Loading commit data... | |
conflicts_service_spec.rb | Loading commit data... | |
diff_spec.rb | Loading commit data... | |
diff_stitcher_spec.rb | Loading commit data... | |
health_check_service_spec.rb | Loading commit data... | |
notification_service_spec.rb | Loading commit data... | |
operation_service_spec.rb | Loading commit data... | |
ref_service_spec.rb | Loading commit data... | |
remote_service_spec.rb | Loading commit data... | |
repository_service_spec.rb | Loading commit data... | |
util_spec.rb | Loading commit data... | |
wiki_service_spec.rb | Loading commit data... |