当我试图逃跑的时候
git push origin master --force
我刚刚
Counting objects: 2649, done.
Delta compression uses up to 2 threads.
Compressing objects: 100% (1280/1280), done.
error: RPC failed; result=22, HTTP code = 413 | 116 KiB/s
fatal: The remote end hung up unexpectedly
Writing objects: 100% (2504/2504), 449.61 MiB | 4.19 MiB/s, done.
Total 2504 (delta 1309), reused 2242 (delta 1216)
fatal: The remote end hung up unexpectedly
Everything up-to-date
这和缺乏安全感有关吗?我尝试创建一个公钥作为致命的答案:远程端意外挂断并重新运行它，但它仍然不工作。我不是在用钥匙吗?如果是，我该如何使用它?
基于您正在使用的推送到回购的协议
HTTP
git config --global http.postBuffer 157286400
引用:
https://git-scm.com/docs/git-config#Documentation/git-config.txt-httppostBuffer
SSH
在~/中添加以下内容。Linux机器中的Ssh /config文件
Host your-gitlab-server.com
ServerAliveInterval 60
ServerAliveCountMax 5
IPQoS throughput
引用:
https://docs.gitlab.com/ee/topics/git/troubleshooting_git.html#check-your-ssh-configuration
https://unix.stackexchange.com/questions/3026/what-options-serveraliveinterval-and-clientaliveinterval-in-sshd-config-exac
https://communities.vmware.com/message/2778248
我收到了与fatal相同的错误消息:远程端意外挂断，没有一个答案解决了我的问题。我通常的工作流程是这样的:
本地签出基本分支(设置了远程源)
从本地的基分支构建子分支
完成我所有的编码
承诺我的东西
按它(然后控制台会告诉我，没有上游设置)
通过git push——set-upstream origin <远程分支名>来设置上游
之后，我的代码通常被推送-但在这种情况下，我有一个提交，我触摸110+文件，我得到了错误。
解决方案:
renaming the current local branch with git branch -m <branch name temp>
checkout base branch (as it best at the same state where the local branch was created)
creating the new child branch with the final name with git checkout -b <branch name>
pushing the new child branch now without any commit, so that it is created at the remote side (also again by git push --set-upstream origin <remote branch name>)
cherrypicking the commits from the <branch name temp> branch
pushing the commits (after checking that I cherrypicked all commits in the right order, the first commit needs to be the first cherrypicked one)
然后就成功了。
希望这也能帮助到这里的一些人!：）
