Warning: file_get_contents(/data/phpspider/zhask/data//catemap/9/git/20.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Git 无效的作者/提交人行-名称不正确_Git_Gitlab - Fatal编程技术网

Git 无效的作者/提交人行-名称不正确

Git 无效的作者/提交人行-名称不正确,git,gitlab,Git,Gitlab,我求助于GitLab论坛,因为在其他存储库中我遇到了这个问题 如果我想将cca 27 000+提交到gitlab的存储库推送到gitlab,我会收到以下错误消息: invalid author/committer line - bad name Git fsck: $ git fsck error in commit 0d4bbd96410dfa6d9d9bf761f26ba7651da38a96: invalid author/committer line - bad name error

我求助于GitLab论坛,因为在其他存储库中我遇到了这个问题

如果我想将cca 27 000+提交到gitlab的存储库推送到gitlab,我会收到以下错误消息:

invalid author/committer line - bad name
Git fsck:

$ git fsck
error in commit 0d4bbd96410dfa6d9d9bf761f26ba7651da38a96: invalid author/committer line - bad name
error in commit 12b631675ee57e6dff9b8a88d701f5fb675124f5: invalid author/committer line - bad name
error in commit 7ce2853ca86fd855d1cd91faa8544d3aeecab64d: invalid author/committer line - bad name
error in commit b5342fe7542caea020a89112a93bb963aae132e2: invalid author/committer line - bad name
error in commit 4077f525f04109e098c53eccde319b96f3335295: invalid author/committer line - bad name
error in commit 1ba710a7bd959908adef4a5d1614efe13e7018d1: invalid author/committer line - bad name
error in commit bd23bd1c5c0607c09d6539edfaa658d12b988261: invalid author/committer line - bad name
error in commit 9923df774580cbba6455face1631074105db9bba: invalid author/committer line - bad name
error in commit e316869ee4c99a437249e4d24e0734d05bfbf9ac: invalid author/committer line - bad name
error in commit 971d617e9e01640a4f2b6d55aba4d98dfd352a76: invalid author/committer line - bad name
error in commit 9629a340c6f8af87d2673ecab6c05d319aac26a5: invalid author/committer line - bad name
error in commit ce1280627d7f075ec7cbd54182089714086f808e: invalid author/committer line - bad name
error in commit 2e6ca81365001c564ef7b4e826d79f951b362385: invalid author/committer line - bad name
error in commit 848dafd3ac203cdddc312825d5a139f95afe4ba5: invalid author/committer line - bad name
error in commit 85d3dc8b719e116d948de66bde26291a8d8c6647: invalid author/committer line - bad name
error in commit 7c4f2f520f4047b10d94e44f6af1c910ff4bdbcf: invalid author/committer line - bad name
error in commit 3b389b8aa2a4dcf916b1151acde4721f429d6199: invalid author/committer line - bad name
error in commit 83500cb1e4388937a98bba1903de37430415ea16: invalid author/committer line - bad name
error in commit 66f5d749c0f72053ddc8f2c9716310102b822f03: invalid author/committer line - bad name
error in commit c5f83416343882ab5a5c1548832dc675e999ad36: invalid author/committer line - bad name
error in commit a32d417cf00ab527f8bfc255c6b2399e855d582d: invalid author/committer line - bad email
error in commit 16565316e4a177d152a64a13db14e7c0c8335c2b: invalid author/committer line - bad email
我只有在Gitlab上有这个问题,在bitbucket推送上没有问题。
我需要帮助我如何解决这个问题。我想把它推到我的存储库。

这次悲伤的聚会我迟到了3年半,但也许你也像我一样来到这里,却找不到答案:)

在我的例子中,我试图移动一个历史悠久、分支众多的大型存储库

很久以前,一些提交人有一个格式不好的作者(比如“John Doe”)。这显然是错误的,但我们年轻时会犯错,对吗

现在gitlab对此抱怨,这是理所当然的

在我的例子中,选择重写整个历史,因为它(存储库)童年犯下的错误,比生活在错误中更糟糕

那么,我们如何让gitlab接受这个错误呢? 一种解决方案是通过以下方式禁用gitlab的检查:

  • 编辑
    /etc/gitlab/gitlab.rb
    并配置在接收时禁用对象git检查的高级选项:
    omnibus_gitconfig['system']={“receive”=>[“fsckObjects=false”]}
  • 重新配置gitlab:
    gitlab ctl重新配置

  • 我知道这个解决方案可能不是每个人都能接受的,但它“对我有效”。希望有人会发现这很有用。

    使用可以绕过此检查。执行第一次同步后,您可以禁用镜像并正常使用存储库。

    尝试“git show…”在一些提交中,查看作者/提交者行的外观。$git show 0d4bbd96410dfa6d9d9bf761f26ba7651da38a96作者:malcromdev@gmail.com>日期:2010年5月18日星期二19:08:08-0230我在您的
    git show的输出中看到两个
    -s。另外请注意,默认情况下,
    git show
    使用
    --format=medium
    ,它只显示作者行,而不显示提交者行。Checkout