diff options
| author | Patrick Steinhardt <psteinhardt@gitlab.com> | 2020-03-10 18:19:29 +0300 |
|---|---|---|
| committer | Patrick Steinhardt <psteinhardt@gitlab.com> | 2020-03-10 18:19:29 +0300 |
| commit | cd501ca5ad38654b39c1d3c3908f4332e08f85d5 (patch) | |
| tree | b7b8ff3de5d1b3aeea502e66f50221554a04e4de | |
| parent | 5dc18b83a860b28199c7f3c5862bbef2411a095d (diff) | |
| parent | a8ebd951bf248c0da2eb6bea2c0afcfe6418f2c6 (diff) | |
Merge branch 'jv-mention-remote-ext' into 'master'
Developer documentation: add note about git-remote-ext
See merge request gitlab-org/gitaly!1897
| -rw-r--r-- | cmd/gitaly-ssh/README.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/cmd/gitaly-ssh/README.md b/cmd/gitaly-ssh/README.md index 74a78a0ca..8bfe7ab0f 100644 --- a/cmd/gitaly-ssh/README.md +++ b/cmd/gitaly-ssh/README.md @@ -8,6 +8,10 @@ installation. It acts as a plugin to `git fetch` using the The implementation shares code with how gitlab-shell handles Git SSH traffic from real users, but it cuts out SSH itself. +> Note for Git experts: in retrospect, we should have used +[git-remote-ext](https://git-scm.com/docs/git-remote-ext) for this, +but we didn't know that mechanism existed at the time. + ## How gitlab-shell does it A normal `git fetch` over SSH goes through these steps. Note that here |