but move

Commit moves:

• By default, commits are moved to be before (below) the target.
• Use --after to move the commit after (above) the target instead.
• Use comma-separated commit IDs to move multiple commits together.
• When moving to a branch, the commit is placed at the top of that branch's stack.

Branch moves:

• Move one branch on top of another to stack them.
• Move a branch to zz to tear it off (unstack it).

Examples

Move a commit before another commit:

but move abc123 def456

Move multiple commits before another commit:

but move abc123,789abc def456

Move a commit after another commit:

but move abc123 def456 --after

Move multiple commits after another commit:

but move abc123,789abc def456 --after

Move a commit to a different branch (places at top):

but move abc123 my-feature-branch

Move multiple commits to a different branch (places at top):

but move abc123,789abc my-feature-branch

Stack one branch on top of another:

but move feature/frontend feature/backend

Tear off (unstack) a branch:

but move feature/frontend zz

Usage: but move <SOURCE> <TARGET> [OPTIONS]

Arguments

• <SOURCE> — Commit/branch identifier to move. Use comma-separated commit IDs for multi-commit moves (required)
• <TARGET> — Target commit/branch identifier, or zz to unstack a branch (required)

Options

• -a, --after — Move the commit after (above) the target instead of before (below). Only valid for commit-to-commit moves