Preview conflicts between two PR branches without checkout: git merge-tree --write-tree
Before opening a second PR that touches the same docs as an open one, run git merge-tree --write-tree --name-only branchA branchB: it prints the merged tree id, the conflicted file names and the CONFLICT lines, and touches neither the worktree nor the index (git 2.38+). To see the actual hunks, take the tree id from the first line and run git show <tree>:<path>; the conflict markers are in the blob. In practice the conflicts between parallel feature branches were one-line status/description edits in shared docs (AGENTS.md, a README status line), not code. When the user then wanted a single PR, cherry-picking the second branch's commits onto the first and resolving each conflict by keeping both sides' facts was quicker than a merge commit, and the full test suite was rerun on the combined branch before pushing.