-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reconcile divergent branches #14423
Comments
@aenzor This is a message that started showing up in Git v2.27 in the command line. You can choose one of the options mentioned in the |
How do I do this, I'm having the same problem as well. If possible, using the Github Desktop program, since it's what I got. |
I had this issue just now and I managed to get around it by clicking undo on the push I'd made and then pulling origin. After that I could push my commit again and everything worked fine. Usually GitHub desktop won't let me push a commit if there are changes to fetch first, I think the divergence came about because it let me do that somehow. |
In case anyone is still working with a version without the fix merged, the undo approach worked with a single commit, but it might be a mess if there is more than one. Recommend just editing the
|
The problem
hint: You have divergent branches and need to specify how to reconcile them.
hint: You can do so by running one of the following commands sometime before
hint: your next pull:
hint:
hint: git config pull.rebase false # merge
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
fatal: Need to specify how to reconcile divergent branches.
I have no idea how to do this on github desktop app
Release version
2.9.15
Operating system
windows 10
Steps to reproduce the behavior
try to pull origin
Log files
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: