land

Landing a branch

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

Two things here are irreversible or outward-facing — opening the PR and writing to main — so the procedure gates each one. A third, deleting the branch from origin, is outward-facing and deliberately not gated; step 9 and references/branch-deletion.md say why, and why that reasoning does not generalise.

1. Preflight

git fetch origin                # origin/main current before anything reads it; no origin at all: references/new-repository.md, before step 2
git status --short              # see below — clean, or knowingly left
git branch --show-current       # must not be main
git log --oneline origin/main..HEAD
git rev-parse origin/main       # <base>, kept like step 7's <sha>: after the merge, nothing else says where main stood
git log --merges --oneline origin/main | wc -l   # the history's merges so far, for step 6
git worktree list               # separate trees — not who shares this one
git branch -vv                  # where HEAD is, and each branch's tip
git rev-parse --path-format=absolute --git-dir --git-common-dir   # two paths: a linked worktree

A dirty tree is not automatically unfinished work. commit ends on a clean tree or on remaining lines it names as intentionally left, so a leftover is a question rather than a stop: ask whether it belongs in this branch. Uncommitted work does not travel into the PR either way — what matters is that nothing which should have been committed is sitting unstaged. Anything you cannot account for, stop and ask.

Nothing to land means there is nothing to do — say so rather than opening an empty PR.

Where the repo's instructions land this branch without a push, follow them instead, unless a push or a PR was asked for: step 3 publishes every unpushed commit beneath the branch. agent-config's .claude/rules/handoff-briefs.md lands a brief's worktree that way.