git 问题解决总结

Hacker_Albert

已于 2023-06-05 10:20:46 修改

阅读量214

点赞数

CC 4.0 BY-SA版权

分类专栏： git 文章标签： git

于 2019-06-25 16:33:35 首次发布

本文链接：https://blog.youkuaiyun.com/weixin_41028621/article/details/93629629

git 专栏收录该内容

1 篇文章

订阅专栏

本文详细解析了在使用Git过程中常见的两个错误：非快速前进更新（non-fast-forward）及远程起源已存在。针对这两个问题，文章提供了具体的操作步骤和解决办法，帮助读者理解错误原因并学会如何处理。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

记录git 问题

1.git push 报错non-fast-forward


$ git push origin master  
To ../remote/  
 ! [rejected]        master -> master (non-fast forward)  
error: failed to push some refs to '../remote/'  
o prevent you from losing history, non-fast-forward updates were rejected
Merge the remote changes before pushing again.  See the 'non-fast forward'
section of 'git push --help' for details.

This error can be a bit overwhelming at first, do not fear. Simply put, git cannot make the change on the remote without losing commits, so it refuses the push. Usually this is caused by another user pushing to the same branch. You can remedy this by fetching and merging the remote branch, or using pull to perform both at once.

In other cases this error is a result of destructive changes made locally by using commands like git commit --amend or git rebase. While you can override the remote by adding --force to the push command, you should only do so if you are absolutely certain this is what you want to do. Force-pushes can cause issues for other users that have fetched the remote branch, and is considered bad practice. When in doubt, don’t force-push.

解决方法：

//强推，即利用强覆盖方式用你本地的代码替代git仓库内的内容
git push -f  origin master

2.上传本地代码到公司gitlab 报错：
执行git remote add origin ssh://xxx/xxx/xxx.git
fatal: remote origin already exists.（报错远程起源已经存在。）

问题：上传的代码已经有远程源。

:~/Documents/openblt$ git remote -v
origin  https://github.com/feaser/openblt.git (fetch)

解决方法：

1、git remote rm origin
2、git remote add origin ssh://xxx/xxx/xxx.git
3、git push origin master