land

Landing a branch

Take a branch that is already committed and get it merged. commit ends by reporting hashes "against a clean tree" with an explicit note that nothing was pushed; this starts exactly there.

Two things here are irreversible or outward-facing — opening the PR and pushing main — so the procedure gates each one.

1. Preflight

git status --short              # must be clean
git branch --show-current       # must not be main
git log --oneline origin/main..HEAD

A dirty tree means commit has not finished. Nothing to land means there is nothing to do — say so rather than opening an empty PR.

Ask whether another session is live in this working tree. Step 7 runs git switch, and one working tree has one HEAD, so the switch is not scoped to you — it moves the branch under anyone else working here. If someone is, stop after step 6 and let them finish.

2. Establish the identity before anything outward

This gates every outward action, and it is the step most likely to fail silently.

git config user.name            # the includeIf identity for this root
gh api user -q .login           # the account gh will actually act as
git remote -v                   # who owns the repo

Then github-mcp → get_me when that server is loaded, and compare every login against the repo owner. Use the tool whose account matches.

On this machine gh is folder-scoped (since 2026-09-04): both shell profiles wrap it to act as the account named by the repo's user.name, resolved per call through a scoped GH_TOKEN, so a personal repo gets the personal account and a client root gets the client one. Two consequences. gh auth status reports the keyring's active account, not the one the wrapper will use — gh api user is the honest probe. And the wrapper is a profile function, so a gh run from a script or hook that skips the profile falls back to the active account; probe through the same shell the PR command will use.