nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I solve a conflict in a pull request?

ramo102

Suppose I have two branches, master and release/2.0, and I want to merge the release branch into master.

I do a pull request to merge release/2.0 to master, but, after the pull request has been done, I discover that there is a conflict (for example, application's version within the main POM).

How can I solve the conflict? Is the previous one (direct pull request in BitBucket) the right approach, or I have to perform the merge in my local environment and then make the pull request? In this case, which are the steps to perform?

Thanks in advance.

Accepted answers

Kristy

You have two options to resolve the conflict:

1) Resolve them without a pull request.

To do this, you would checkout the master branch, and then pull in the release branch. This is effectively the solution that Bitbucket Server give you when you ask for more information on how to solve the conflict.

$ git checkout master
$ git pull origin release/2

<resolve merge conflicts and commit>

$ git push

2) Resolve them with a pull request

To do this, you would create a branch off the tip of master, pull in the release branch and create a pull request from that branch to master. This is the best option if you don't have permission to push directly to master.

$ git checkout master
$ git checkout -b resolve-conflicts-branch
$ git pull origin release/2

<resolve merge conflicts and commit>

$ git push -u origin resolve-conflicts-branch

<create pull request>

Note: Once you have resolve the conflicts through either of these methods, your old pull request from release/2 to master will be closed automatically since there will no longer be any diff.

All comments

Tim Crall1

perform the merge in reverse locally, merging master into release/2

git checkout release/2
git merge master

then manually resolve any conflicts, commit and push

git commit
git push

Your pull request should automatically update itself to the new commit and there are no longer any conflicts (because you just resolved them all)

BETTER YET

You could also use a rebase instead of a merge. This gives a cleaner look to your history, at the cost of a little bit of historical accuracy. Many people think that's a good deal.

git checkout release/2
git rebase master
&lt;resolve conflicts manually&gt;
git push

As before, your Pull Request should now be mergeable

ramo102

Hi @Tim Crall,

I need to merge the release branch into master; does your solution do the opposite?

Tim Crall1

It does the opposite locally as a means of resolving the conflicts between them. It then uses the Pull Request to do the actual merge in the correct direction.

Kristy

When you push onto release/2 you are have effectively merged master into release/2. This is not what you want to do if you would like your release branch to not contain all the commits that exist on master.

Kristy

You have two options to resolve the conflict:

1) Resolve them without a pull request.

$ git checkout master
$ git pull origin release/2

<resolve merge conflicts and commit>

$ git push

2) Resolve them with a pull request

$ git checkout master
$ git checkout -b resolve-conflicts-branch
$ git pull origin release/2

<resolve merge conflicts and commit>

$ git push -u origin resolve-conflicts-branch

<create pull request>

Note: Once you have resolve the conflicts through either of these methods, your old pull request from release/2 to master will be closed automatically since there will no longer be any diff.

ramo102

The second solution is fine for me.

Mohammed Davoodi

We've developed a plugin, Power Editor for Bitbucket, that allows you to resolve conflicts on a pull request in the UI. You won't need to go through any of the git commands anymore smile (even though we highly recommend you learn them, they can be quite useful). You can check out out here.

It also supports:

Adding, renaming and deleting files
Editor extensions like preview, view diff and tab and space controls.
Editing functionality in pull requests to quickly fix typos in files.
Full support for hooks.

Stefan Wendelmann

1) Works for me, before i push i had to commit

Casey Wise

I resolve locally, w/ a non-fast forward merge from the target branch into the source branch. A word about non-fast forward merges, they create an easily rescinded commit should you require a rollback.

1. Checkout to master, get latest, checkout to your release/2.0 and non-fast forward merge master in to it:

git checkout master && git pull && git checkout release/2.0 && git merge --no-ff master

2. Your output will indicate which files are conflicting. Iron out those conflicts.

3. Commit the conflict resolution, push your release branch back up for a clean pull request.

git commit -am "resolve merge conflict" && git push

Kristy

@Casey Wise, maybe I'm misunderstanding your comment but it seems to me that this will result in all the changes from master being on the release branch.

If you then want to make a bugfix to that release branch, you may not get what you expect because it will contain all the changes from master too - which may be API breaking, contain extra features etc and is against the rules of SemVer.

Casey Wise

@Kristy If there's broken or unnecessary code on master you don't want cleanly merging w/ your release/feature/hotfix, someone owes the office donuts and/or bagels!

git blame

Kristy

Its not that there is broken code on master, but that the release branches should be strictly behind master. Master will contain the newest features, which you might not want merged into old release branches for the sake of compatibility.

M S_t1gnyp

Why is there no online web GUI app that makes the merging easier?

I don't want to deal with command line when needing to resolving conflicts. GitHub already has an online tool that does that.

Kristy

There is a feature request for this you can vote on and watch: https://jira.atlassian.com/browse/BSERV-4617

David Latty

The problem is if any of the merged code is postponed or abandoned (e.g. to requirement needs) your master ends up with code - and this is bad as that code may likely be issued. It may also not have been the last commit. What happens then?

Carol Skelly

But solution 1 pushes back to master and closes the pull request which we don't want if the PR is still pending review/approval, correct?

Kidane Yosief_ree4u0

you would need to resolve the conflict in your branch first.

git checkout yourBranch

git merge origin/master

resolve your conflict

git add . && git commit -m "conflict resolve" && git push

This way your pull request will look fine.

it can be reviewed and merged perfectly ...

Kristy

This would usually work for most branches, however the example that has been posted is for a release branch merging into master. Most of the time, there would be branch permissions set up to stop you from pushing directly to release branches so this approach may not work in those cases where you do not have permission to push to the branch.

Christiana Parker_hosk1w

When you have merge conflicts, you can't click the Merge button from the pull request to merge. To resolve these conflicts, you pull the changes to your local repository and fix them there. beside this if you've Forgot Roadrunner Password so don't worry about it just check the link to make every issue solve by experts.

Kristy

In this case, I believe the question was about a pull request from a `release/` branch. In this case, you wouldn't want to pull the target branch into the source branch because the `release/` branches should always be behind the target branch

Johnson Clarke

Using this code on homepage of my site.

$ git checkout master
$ git pull origin release/2

<resolve merge conflicts and commit>

$ git push

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

bitbucket-server

atl-gruland

bitbucket-development