- There exist a develop branch and feature1 branch that were in sync
- Then, I committed a few changes in the develop branch, by mistake (3 commits to be precise)
- I then switched to feature1 branch and cherry picked the few changes (3 commits).
- Then i made a few changes in the feature1 branch ( 1 new commit).
- I Created a PR for merging feature1 into develop (feature1 ===>> develop).
The Files Changed section of the pr now shows changes that i had cherry picked ( the changes in the 3 commits).
But develop already has those changes.
I evidently cherry picked the changes from develop itslef. Then why does a pr show chages that are already present in the branch that i cherry picked from.
Possible Reason
Is it because cherry pick creates a new commit hash. Github compares the branches by commit hash and since it finds a new hash It just shows the changes done in the new hash
An answer on Microsoft develop community also shows, How github compares two branches?