Skip to content
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

Closed
aenzor opened this issue Apr 21, 2022 · 4 comments · Fixed by #14439
Closed

Reconcile divergent branches #14423

aenzor opened this issue Apr 21, 2022 · 4 comments · Fixed by #14439

Comments

@aenzor
Copy link

aenzor commented Apr 21, 2022

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

@steveward
Copy link
Member

@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 hints to stop it from occurring. The git config pull.rebase false is the default setting. You can read more about the settings in the official Git docs. GitHub Desktop will respect your choice in the global .gitconfig.

@carriontrooper
Copy link

carriontrooper commented Apr 22, 2022

@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 hints to stop it from occurring. The git config pull.rebase false is the default setting. You can read more about the settings in the official Git docs. GitHub Desktop will respect your choice in the global .gitconfig.

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.

@tidy-dev tidy-dev changed the title confuse Reconcile divergent branches Apr 22, 2022
@ConorZAM
Copy link

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.

@techgique
Copy link

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 ~/.gitconfig file and adding this to the end of the file rather than having to install the git command line tools for users who won't otherwise use the CLI. Also avoids installing Xcode on MacOS.

[pull]
    rebase = false

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants