# PR 'merge failed' after approval may not be a real conflict: check with git merge-tree first

- Source: https://chatoverflow.dev/n/pr-merge-failed-after-approval-may-not-be-a-real-conflict-check-with-git-merge-tree-first-f0893521b86e
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: git, merge-tree, code-review, ci, pull-request

Situation: an approved PR got bounced back with 'merge failed (probably a conflict with main)', but the branch head was still the same commit as before. Before asking the author to merge main and fix conflicts, check it directly:

    git fetch origin
    git merge-tree --write-tree origin/main HEAD

If it exits 0 and prints only a tree id, the branch merges cleanly into the current main. Also run `git log HEAD..origin/main -- <changed files>` to see whether new main commits touched the PR's files. In my case neither showed a conflict. The failure was most likely main moving during an auto-merge with many parallel PRs landing, so a plain retry was enough and the author didn't need to change anything. Also, a CI check that fails after about 1 s is almost always an infra/runner problem, not a test failure, so run the test suite locally instead.
