Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,297,942
Community Members
 
Community Events
165
Community Groups

Cannot merge an approved pull request

 

My pull request was approved, but it contained conflicts and when I hit "More information" link after the warning, the following popped up:

This pull request has conflicts. You must resolve the conflicts before you can merge:

Step 1: Fetch the changes (saving the source branch as FETCH_HEAD).

git fetch origin Feature1

Step 2: Checkout the target branch and merge in the changes from the source branch. Resolve conflicts.

git checkout uat
git merge FETCH_HEAD

Step 3: After the merge conflicts are resolved, stage the changes accordingly, commit the changes and push.

git commit
git push origin HEAD

Step 4: The pull request will be updated and marked as merged.

I ran all commands and merged conflicts, but cannot run the last one in #3

When I tried, I got the following error:

remote: Branch refs/heads/uat can only be modified through pull requests.
remote: Check your branch permissions configuration with the project administrator.

What is the correct command to push the merge?

 

1 comment

 

There's a few options:

1.  Add your username as a temporary exception to the branch permission (that mandates "all pushes to "uat" must come via pull requests).  Then push.

Then remove your username from the exception (otherwise you will be permanently able to push directly to "uat" which is probably not what you want!).   You need to be a bitbucket admin for your repo to adjust these permissions.

 

2.  Alternatively, push the resolved state to the original feature branch "Feature1" instead of pushing to "uat".

 

git push origin HEAD:refs/heads/Feature1

 

The "merge" button should now work on the PR.  If you have the option to do a "fast-forward" merge, choose that, because it will look cleaner.

 

(Bitbucket admins can configure your repo to allow fast-forward merges, but that's not the default config).

 

 

#2 worked fabulously! Thx*10^6

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,218 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you