After “git rebase origin/master” and “git push -f”, many commits in the master branch are shown in the pull request some time.
This issue was happened in GH-16430. But I had seen similar issues several times.
I asked the Github support about it, and I got the answer from them:
Stacey Burns (GitHub Developer Support) Oct 30, 1:18 PM UTC
We use what’s called a “three-dot diff” on a Pull Request, which is the
difference between the latest commit on the Pull Request branch and the last common ancestor commit
with the base branch. The last common ancestor is also derived at the
time the Pull Request is created, and doesn’t change throughout the Pull
At the time the Pull Request was created, the base branches head commit was . The author then modified the Pull Request branch head commit to , which results in the following diff:
an existing Pull Request can result in undesirable / unintended results
in some cases, especially when the Pull Request branch is far behind
the base. We normally encourage folks to make sure their Pull Request
branch is up to date with the base branch before creating the Pull Request. This ensures the last common ancestor is the most up to date.
I hope this is somewhat helpful! If there’s anything else I can do to help, please let me know.