From: <rsbecker@nexbridge.com>
To: <jjb8256@sina.com>, <git@vger.kernel.org>
Subject: RE: git push error
Date: Wed, 20 Mar 2024 07:52:03 -0400 [thread overview]
Message-ID: <02ef01da7abd$0a33b760$1e9b2620$@nexbridge.com> (raw)
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
next prev parent reply other threads:[~2024-03-20 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 7:17 git push error jjb8256
2024-03-20 8:45 ` Kristoffer Haugsbakk
2024-03-20 8:51 ` Kristoffer Haugsbakk
2024-03-20 11:52 ` rsbecker [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-18 7:30 Git " Marcus
2008-05-18 8:09 ` Peter Baumann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='02ef01da7abd$0a33b760$1e9b2620$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=jjb8256@sina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).