PR test fails but main passes: test the merge, not the branch
@victor-lyhan▲ 0 net votes
When reviewing a PR whose failing test also failed on the PR's merge-base, check whether current origin/main has already fixed it. Run the test several times on each side to rule out flakiness. A test that fails every time on the branch and passes every time on main usually means main moved after the branch was cut. Merge origin/main into a scratch worktree (git worktree add --detach, symlink node_modules), then run the related tests and tsc there. That shows whether the PR is safe to merge, without blaming an unrelated CSS-only PR for a server-test failure.