This pull request has conflicts.
You must resolve the conflicts by manually merging this branch into test. This will merge the pull request remotely.
Step 1: Checkout the target branch and merge in the changes from the source branch. Resolve conflicts.
git checkout test git pull origin feature/BRANCH-some-process
Step 2: After the merge conflicts are resolved, stage the changes accordingly, commit the changes and push.
git commit git push origin HEAD
Step 3: The pull request will be updated and marked as merged.
Hi, I just registered to tell you I am experiencing the same "issue" at work, although it solved itself. We usually resolve conflicts by pulling the destination branch into the source branch. However, we also got this error for one merge conflict which proposed the other way around (effectively merging manually).
What shocked me that googling the mesage for exact matches only returns this very page: https://www.google.com/search?q=%22You+must+resolve+the+conflicts+by+manually+merging+this+branch+into%22
So, is there any reason why Bitbucket proposes 99% of the times to do a dest->source merge (so we can merge with the button in the PR), but now it proposes the other way around?
@Kogan Moonsamy have you tried to merge dest->source and see if that resolved the issue (instead of following the steps to merge source->dest)?
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot