Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,463,408
Community Members
 
Community Events
176
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

Atlassian Community Events