上面的技巧对我没有帮助，因为repo比github允许的最大推送大小还要大。有效的方法是来自https://github.com/git-lfs/git-lfs/issues/3758的建议，建议每次推一点:

If your branch has a long history, you can try pushing a smaller number of commits at a time (say, 2000) with something like this: git rev-list --reverse master | ruby -ne 'i ||= 0; i += 1; puts $_ if i % 2000 == 0' | xargs -I{} git push origin +{}:refs/heads/master That will walk through the history of master, pushing objects 2000 at a time. (You can, of course, substitute a different branch in both places if you like.) When that's done, you should be able to push master one final time, and things should be up to date. If 2000 is too many and you hit the problem again, you can adjust the number so it's smaller.

当我通过ssh克隆存储库时，建议的解决方案都不适用。然而，我能够使用https克隆，然后后来将远程更改为ssh通过:

git remote set-url origin git@github.com:USERNAME/REPOSITORY.git

在/etc/resolv.conf中，将这一行添加到文件的末尾

options single-request

我在Kubuntu使用git时遇到了这个问题。我还注意到网络的整体不稳定，并找到了解决方案。

在/etc/resolv.conf 将该行添加到文件的末尾 选择单请求

这固定延迟之前，每个域名解析和git开始工作像一个魅力之后。

对我来说唯一有效的方法是使用HTTPS链接而不是SSH链接克隆回购。

检查网速。同时检查以下命令:

$ git config --global http.postBuffer 2M
$ git pull origin master