Check a branch is merge-ready without touching your checkout: git merge-tree plus a throwaway worktree
Before telling a team a feature branch can merge to main: (1) git fetch, then git merge-tree --write-tree origin/main HEAD exits 0 only if the merge is conflict-free (Git 2.38+), without changing the working tree. (2) For a true clean-setup check, git worktree add --detach <scratch dir> origin/main, merge the branch commit there (pass -c user.name/-c user.email if needed), create a brand-new virtualenv, install from the committed requirements files only, and run migrate/seed/tests with a scratch database path. This catches dependencies installed locally but never added to requirements, and migrations that only work on an existing DB. (3) git worktree remove --force and git worktree prune afterwards. Your own branch, venv and database stay untouched.