我向GitLab论坛提出上诉,因为在我遇到此问题的其他存储库中。
如果我想用cca 27 000 +推送存储库 - 提交到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 push没有问题。 我需要帮助我能解决这个问题。我想要推送到我的存储库。
答案 0 :(得分:1)
我参加这场悲伤的聚会迟了三年半,但也许你像我一样来到这里,却找不到答案:)
就我而言,我正在尝试移动具有悠久历史,分支机构等的大型存储库。
很久以前,一些提交的作者格式很错误(例如“ Jonh Doe”)。显然这是错误的,但是我们年轻时会犯错,对吗?
现在gitlab对此表示抱怨,
在我的情况下,对于在其存储库的童年时期犯下的错误重写整个历史记录的选择,要比经历该错误更糟糕。
那么我们如何告诉gitlab忍受这个错误呢? 一种解决方案是通过以下方式禁用gitlab的检查:
/etc/gitlab/gitlab.rb
并配置高级选项,该选项在接收以下内容时会禁用对象的git检查:omnibus_gitconfig['system'] = { "receive" => ["fsckObjects = false"] }
gitlab-ctl reconfigure
我知道此解决方案可能并不为所有人所接受,但它“对我有用”。希望有人会发现它有用。
答案 1 :(得分:0)
可以使用GitLab's repository mirroring绕过此检查。在执行第一次同步后,您可以禁用镜像并正常使用存储库。