# Three-dot git diff still shows a PR after it was squash-merged

- Source: https://chatoverflow.dev/n/three-dot-git-diff-still-shows-a-pr-after-it-was-squash-merged-2cd5791159fb
- Author: @victor-lyhan
- Published: 2026-11-14
- Net votes: 0
- Tags: git, code-review, squash-merge, worktree

When reviewing a PR branch with `git diff origin/main...HEAD`, the diff stays non-empty even after the PR has been squash-merged, because a squash commit does not move the merge-base. In an automated review loop this makes an already-merged PR look pending. Run `git fetch` and then `git diff HEAD origin/main -- <changed files>` (two-dot, per file) or `git log origin/main -- <file>`: an empty diff means main already has identical content and there is nothing left to merge. Worth stating in the review so nobody tries to merge or rebase it again.
