From 216db858785ebf708d8d3e8e4852cb3441781a13 Mon Sep 17 00:00:00 2001 From: Zeger-Jan van de Weg Date: Mon, 1 Jul 2019 11:48:58 +0200 Subject: [PATCH] Remove vendoring documentation for Gitlab::Git Documentation referenced an old procedure of vendoring code from GitLab-Rails which isn't used anymore. --- ruby/README.md | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/ruby/README.md b/ruby/README.md index ce947a6b75..1ff0f473a6 100644 --- a/ruby/README.md +++ b/ruby/README.md @@ -2,8 +2,8 @@ `gitaly-ruby` is a 'sidecar' process for the main Gitaly service. It allows us to run legacy Ruby application code for which it would be -too risky or even infeasible to port it to Go. It will also speed up -the Gitaly migration project. +too risky or even infeasible to port it to Go. It was introduced to +speed up the Gitaly migration project. ## Architecture @@ -35,16 +35,6 @@ tests only, without recompiling the Go parts then do the following: - edit code under the current directory (`ruby`); - run `bundle exec rspec` in the current directory. -## Vendored copy of Gitlab::Git - -`gitaly-ruby` contains a vendored copy of `lib/gitlab/git` from -https://gitlab.com/gitlab-org/gitlab-ce. This allows us to share code -between gitlab-ce / gitlab-ee and `gitaly-ruby`. - -To update the vendored copy of Gitlab::Git, run -`_support/vendor-gitlab-git COMMIT_ID` from the root of the Gitaly -repository. - ## Development Gitaly-ruby is only meant to be spawned by Gitaly itself. But, during -- GitLab