Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


git cherry pick command confuses bitbucket

Here is a scenario that looks like a defect in bitbucket.


Have 2 branches in bitbucket repo

1. develop   2. release


One commit that was present in develop branch, i used the git cherry pick command to push to release branch.  Once that is done, the same commit is now present in release and develop both.

Even after this, if i raise a pull request from develop to release the same commit still shows up in the differences. 

I think this is a defect on bitbucket side, and should be fixed. Happy to hear what others think about this.

1 answer

1 vote
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 11, 2022

Hi @sanjaytest and welcome to the community.

A few months ago we changed our diff algorithm from what we call a '3-way' diff to a 2-way 'three-dot' diff:

The previous diff algorithm included changes in the destination branch. The new diff algorithm does not reflect changes made to the destination branch since the source branch was created from the destination branch. This change allowed us to improve performance on complex diffs.

If you want to see changes made to the destination branch, you can simply merge the destination branch into the source branch. The blog post I shared has instructions on how to do so in the section "How to see changes to the destination branch in a pull request".

We have a request in our issue tracker for offering the option to preview the previous type of diff on demand:

You can add your vote and comment there to further express your interest.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events