We’re seeing an issue with how pull requests are performed by GitHub. When we model a pull request after previously merging a change from one branch into another, it’s previewing the same “diff” as before, even though we can show the previous change was indeed already made to the branch. GitHub seems to get into this infinite loop of trying to reapply the same change as already merged each time we model the pull request, regardless of how many times we try to merge it. And when each such pull request is actually merged, git in fact does the right thing: nothing! The supposed merge commit will show “0 Changed files with 0 additions and 0 deletions”. Why is GitHub lying to us about what the differences are between our 2 branches?
That seems like a bug. You might want to report that here: https://github.com/contact.
Yes, I agree. GitHub seems to think this is a design feature, however. Their response when I posted via that form, below. From my persepctive though it’s still giving an incorrect answer. It’s showing a difference when there actually isn’t one, and then offering to do a merge assuming that difference, which ultimately results in a no-op because there actually isn’t one. Definitely feels like a bug to me too!
"When you merge commits from a Pull Request into a branch, the commit SHA changes from what the original commit SHA’s were.
This means when you compare the same two branches again, the diff will show those commits again because those specific commit SHA’s don’t exist on the branch you’re merging into.
This is a result of the type of diff we use on GitHub. We use git’s three dot diff, which is the difference between the latest commit on the HEAD branch and the last common ancestor commit with the base branch.
This workflow is designed for a topic branch model. The presumption with the topic branch flow is that a branch is created to merge in a specific feature. Once the branch has been merged it would be deleted and further development would be made on a new branch.
A lot of teams use a master > dev branch model though and for this, once a Pull Request is merged, the master branch would be merged back onto dev using the command line:
git checkout devgit rebase master Rebasing the master back onto dev updates dev with the latest commits from master and should give you a clean diff again.!"
great explaination for the github diff mechanism!
Just checked this locally by:
creating a repo with 1 file and committing it to commit “A”, in master
Checkout to a new branch called “mybranch” and do a
git reset head~1
Make a new commit to commit “B” with the exact same content as “A”
git diff master(on mybranch) gives no results, as expected.
Apologies for resurrecting an old thread, but wouldn’t rebasing master back onto dev change the history of dev, and make it necessary for team members working off dev to take recovery measures?
We recently experienced this issue. Git hub shows an incorrect diff on a bug fix to a minor release. Using git diff between the tags on the command line showed the correct diff.
@[kirkwatrous] GitHub’s explanation for 2 years ago actually explains it in terms of SHA numbers, although I can’t say I agree with the concept.
diff is literal and there’s nothing “implied” in it regarding what is the diff it should be showing.
Squashed merges already have all the content of the topic branch that previously had a PR. That means that computing a diff that the same content again (albeit having a different SHA) is incorrect by the definition of the word “difference”.
When this can be fixed ?
To see the difference that doesn’t really exist is really anonying. It’s not a feature.