Git Push突然卡住无法推进，请求技术协助

问题详情 #

处理ILoveDotNet/ilovedotnet仓库时，Git Push突然无响应：

• 主分支推送执行到remote: Resolving deltas: 100% (3/3), completed with 3 local objects.后卡住，无后续输出
• 创建测试分支执行git push --set-upstream origin test，输出Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)后同样卡住

主分支操作日志：

PS C:\Repos\ilovedotnet> git add .
PS C:\Repos\ilovedotnet> git commit -m "test"
[main 2f5026ae8] test
 1 file changed, 1 insertion(+), 1 deletion(-)
PS C:\Repos\ilovedotnet> git push
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 2 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 348 bytes | 174.00 KiB/s, done.
Total 4 (delta 3), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.

测试分支操作日志：

1234@Abdul-ka-MacBook-Pro ilovedotnet % git checkout -b test
Switched to a new branch 'test'
1234@Abdul-ka-MacBook-Pro ilovedotnet % git push                   
fatal: The current branch test has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin test

To have this happen automatically for branches without a tracking
upstream, see 'push.autoSetupRemote' in 'git help config'.

1234@Abdul-ka-MacBook-Pro ilovedotnet % git push --set-upstream origin test
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)

排查解决步骤 #

1. 验证远程仓库配置 #

检查远程仓库地址是否正确：

git remote -v

若地址异常，重新设置为SSH格式（优先推荐，避免HTTPS认证/代理问题）：

git remote set-url origin git@github.com:ILoveDotNet/ilovedotnet.git

2. 关闭本地代理与防火墙 #

临时关闭VPN、代理软件或系统防火墙，排除网络拦截导致的推送卡住。

3. 清理Git代理配置 #

检查并清除可能存在的HTTP/HTTPS代理配置：

# 查看当前代理配置
git config --global --get http.proxy
git config --global --get https.proxy

# 清除代理配置
git config --global --unset http.proxy
git config --global --unset https.proxy

4. 检查远程仓库钩子 #

远程仓库的post-receive等钩子脚本异常可能导致推送无响应，可联系仓库管理员检查钩子状态，或尝试推送空提交测试：

git commit --allow-empty -m "test empty commit"
git push

5. 重置本地分支与远程同步 #

重置本地分支到远程最新状态，重新操作：

git fetch origin
git reset --hard origin/main
# 重新修改代码、提交、推送

6. 确认GitHub服务状态 #

检查GitHub官方状态页面，确认对应区域的仓库服务是否正常。

7. 切换传输协议 #

若当前用HTTPS协议，切换为SSH协议：

• 生成SSH密钥并添加到GitHub账户
• 执行步骤1中的命令设置SSH远程地址
• 重新尝试推送

内容的提问来源于stack exchange，提问作者fingers10