Commit 97a7e3e0 authored by Zeger-Jan van de Weg's avatar Zeger-Jan van de Weg

Docs: Remove porting to go section for hooks

Through 13.2 until 13.4 there was a while where the implementation
language for the Git Hooks were important as the administrator could use
feature flags go change the behaviour to Ruby. This has since been
removed, so this section of the docs can be removed too.
parent af6e6aa7
...@@ -156,22 +156,6 @@ NOTE: **Note:** ...@@ -156,22 +156,6 @@ NOTE: **Note:**
While other environment variables can be passed to server hooks, your application should not rely on While other environment variables can be passed to server hooks, your application should not rely on
them as they can change. them as they can change.
## Transition to Go
> - Introduced in GitLab 13.2 using feature flags.
> - In GitLab 13.4, `update` Ruby [implementation removed](https://gitlab.com/gitlab-org/gitaly/-/merge_requests/2501).
> - In GitLab 13.4, `post-receive` Go implementation [made default](https://gitlab.com/gitlab-org/gitaly/-/merge_requests/2502).
The following server hooks have been re-implemented in Go:
- `pre-receive`, with the Go implementation used by default. To use the Ruby implementation instead,
[disable](feature_flags.md#enable-or-disable-the-feature) the `:gitaly_go_preceive_hook` feature
flag.
- `update`, with Go implementation always used. No Ruby implementation is available.
- `post-receive`, with the Go implementation used by default. To use the Ruby implementation
instead, [disable](feature_flags.md#enable-or-disable-the-feature) the
`:gitaly_go_postreceive_hook` feature flag.
## Custom error messages ## Custom error messages
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5073) in GitLab 8.10. > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5073) in GitLab 8.10.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment