# git push error

4 messages from 2024-03-20 to 2024-03-20. Participants: jjb8256@sina.com, Kristoffer Haugsbakk, rsbecker@nexbridge.com.
Thread: https://gitlist.dev/t/61159

## jjb8256@sina.com, 2024-03-20 07:17

Subject: git push error
Message-ID: <65fa8d7a469967.62182104.7cc8fd91@m1.mail.sina.com.cn>
URL: https://gitlist.dev/e/65fa8d7a469967.62182104.7cc8fd91%40m1.mail.sina.com.cn

```
Hi：
    git push 时发现如下报错，尝试无法修改，请帮忙，谢谢！

$ git push
Enumerating objects: 9, done.
Counting objects: 100% (8/8), done.
Delta compression using up to 8 threads
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 701 bytes | 233.00 KiB/s, done.
Total 5 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
remote: The gitlab-shell hooks have been migrated to Gitaly, see https://gitlab.com/gitlab-org/gitaly/issues/1226
To http://10.11.15.10/ks-rd-fw/git-train-2022.git
 ! [remote rejected] develop -> develop (pre-receive hook declined)
error: failed to push some refs to 'http://10.11.15.10/ks-rd-fw/git-train-2022.git'
```

## Kristoffer Haugsbakk, 2024-03-20 08:45

Subject: Re: git push error
Message-ID: <6f4d8a42-341b-40e0-97f4-157d053c0ff2@app.fastmail.com>
URL: https://gitlist.dev/e/6f4d8a42-341b-40e0-97f4-157d053c0ff2%40app.fastmail.com
In-Reply-To: <65fa8d7a469967.62182104.7cc8fd91@m1.mail.sina.com.cn>

```
On Wed, Mar 20, 2024, at 08:17, jjb8256@sina.com wrote:
> Hi：
>     git push 时发现如下报错，尝试无法修改，请帮忙，谢谢！
>
> $ git push
> Enumerating objects: 9, done.
> Counting objects: 100% (8/8), done.
> Delta compression using up to 8 threads
> Compressing objects: 100% (5/5), done.
> Writing objects: 100% (5/5), 701 bytes | 233.00 KiB/s, done.
> Total 5 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
> remote: The gitlab-shell hooks have been migrated to Gitaly, see
> https://gitlab.com/gitlab-org/gitaly/issues/1226
> To http://10.11.15.10/ks-rd-fw/git-train-2022.git
>  ! [remote rejected] develop -> develop (pre-receive hook declined)
> error: failed to push some refs to
> 'http://10.11.15.10/ks-rd-fw/git-train-2022.git'

The pre-receive hook on the server failed. That means that whatever you
pushed is wrong according to that script.

See `man githooks`.

--
Kristoffer

```

## Kristoffer Haugsbakk, 2024-03-20 08:51

Subject: Re: git push error
Message-ID: <911b6647-301b-45a3-9f10-f91ed7482eb7@app.fastmail.com>
URL: https://gitlist.dev/e/911b6647-301b-45a3-9f10-f91ed7482eb7%40app.fastmail.com
In-Reply-To: <6f4d8a42-341b-40e0-97f4-157d053c0ff2@app.fastmail.com>

```
On Wed, Mar 20, 2024, at 09:45, Kristoffer Haugsbakk wrote:
> On Wed, Mar 20, 2024, at 08:17, jjb8256@sina.com wrote:
>> [snip]
>> https://gitlab.com/gitlab-org/gitaly/issues/1226
>> [snip]
>
> The pre-receive hook on the server failed. That means that whatever you
> pushed is wrong according to that script.
>
> See `man githooks`.
>
> --
> Kristoffer

You should also look at the the message that the remote sent:

    remote: The gitlab-shell hooks have been migrated to Gitaly, see
    https://gitlab.com/gitlab-org/gitaly/issues/1226

```

## rsbecker@nexbridge.com, 2024-03-20 11:52

Subject: RE: git push error
Message-ID: <02ef01da7abd$0a33b760$1e9b2620$@nexbridge.com>
URL: https://gitlist.dev/e/02ef01da7abd%240a33b760%241e9b2620%24%40nexbridge.com
In-Reply-To: <65fa8d7a469967.62182104.7cc8fd91@m1.mail.sina.com.cn>

```
On Wednesday, March 20, 2024 3:17 AM, jjb8256@sina.com wrote:
>    git push 时发现如下报错，尝试无法修改，请帮忙，谢谢！
>
>$ git push
>Enumerating objects: 9, done.
>Counting objects: 100% (8/8), done.
>Delta compression using up to 8 threads
>Compressing objects: 100% (5/5), done.
>Writing objects: 100% (5/5), 701 bytes | 233.00 KiB/s, done.
>Total 5 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
>remote: The gitlab-shell hooks have been migrated to Gitaly, see
>https://gitlab.com/gitlab-org/gitaly/issues/1226
>To http://10.11.15.10/ks-rd-fw/git-train-2022.git
> ! [remote rejected] develop -> develop (pre-receive hook declined)
>error: failed to push some refs to 'http://10.11.15.10/ks-rd-fw/git-train-2022.git'

This looks like a problem with the pre-receive hook on your GitLab installation on the server-side, or that script is rejecting the push. This probably should be referred to the GitLab team for support (possibly at your company).

--Randall


```