git-branchless-move(1)

💅 move — git-branchless-move(1) 💅

okay bestie, welcome to the git-branchless-move(1) page from the General Commands Manual — it’s giving “relocate your whole commit stack” energy and honestly? iconic. 🫶

---

🌸 NAME 🌸

move — Move a subtree of commits from one location to another. literally picking up your little commit family and moving it somewhere new 💖

---

✨ SYNOPSIS ✨

move [-s|--source] [-b|--base] [-x|--exact] [-d|--dest] [--hidden]
[-f|--force-rewrite] [--in-memory] [--on-disk]
[--no-deduplicate-commits] [-m|--merge] [--reparent]
[--debug-dump-rebase-constraints] [--debug-dump-rebase-plan]
[-F|--fixup] [-I|--insert] [--dry-run] [-h|--help]

---

🦋 DESCRIPTION 🦋

Move a subtree of commits from one location to another. that’s the whole mission, and it ate 💅

By default, git move tries to move the entire current stack if you don’t pass a --source or --base option — that’s equivalent to writing --base HEAD, iykyk.

By default, git move attempts to rebase all commits in-memory. If you want to force an on-disk rebase, pass the --on-disk flag. Note: post-commit hooks are not called during in-memory rebases. no cap, that’s important 🎀

---

👑 OPTIONS 👑

• -s, --source <SOURCE> — The source commit to move. This commit, and all of its descendants, will be moved. the whole little family tree comes with it 🌳
• -b, --base <BASE> — A commit inside a subtree to move. The entire subtree, starting from the main branch, will be moved, not just the commits descending from this commit. so it’s not just the direct kids — the whole branch situation gets relocated 💫
• -x, --exact <EXACT> — A set of specific commits to move. These will be removed from their current locations and any unmoved children will be moved to their nearest unmoved ancestor. very “pick me” behavior, but for commits 🎯
• -d, --dest <DEST> — The destination commit to move all source commits onto. If not provided, defaults to the current commit. so if you don’t choose a destination, it just says “current commit, you’re the main character now” 👑
• --hidden — Include hidden commits in the results of evaluating revset expressions. the hidden girlies get to show up to the function 🙈
• -f, --force-rewrite — Force moving public commits, even though other people may have access to those commits.

⚠️ okay so this one is literally called “force” for a reason — public commits are public, bestie. move them only if you’re ready for the consequences 💀

• --in-memory — Only attempt to perform an in-memory rebase. If it fails, do not attempt an on-disk rebase. it’s giving “in-memory or nothing” ✨
• --on-disk — Skip attempting to use an in-memory rebase, and try an on-disk rebase directly. straight to disk, no in-memory warm-up 💅
• --no-deduplicate-commits — Don’t attempt to deduplicate commits. Normally, a commit with the same contents as another commit which has already been applied to the target branch is skipped. If set, this flag skips that check. so yes, it can absolutely let the duplicate little guys through 🫶
• -m, --merge — Attempt to resolve merge conflicts, if any. If a merge conflict occurs and this option is not set, the operation is aborted. no --merge, no conflict-resolution fantasy — it just stops 😭
• --reparent — Keep all contents of descendant commits exactly the same (i.e. "reparent" them). This can be useful when applying formatting or refactoring changes. Use with care if the descendants are moved from a far-away branch, as it may carry along a lot of unintended changes onto the destination.

⚠️ use with care, fr fr — far-away branches can drag unintended changes onto the destination like an overpacked suitcase 🧳

• --debug-dump-rebase-constraints — Debugging option. Print the constraints used to create the rebase plan before executing it. nerdy and useful, we love her 🔍
• --debug-dump-rebase-plan — Debugging option. Print the rebase plan that will be executed before executing it. preview the plan before the plan does its thing 👀
• -F, --fixup — Combine the moved commits and squash them into the destination commit. tiny commits go in, one destination commit comes out 🍓
• -I, --insert — Insert the subtree between the destination and it’s children, if any. Only supported if the moved subtree has a single head. single head only, bestie — that’s the rule 💫
• --dry-run — Test whether an in-memory rebase would succeed. a little rehearsal before the real performance 🎭
• -h, --help — Print help (see a summary with '-h'). the classic “help me help you” moment 💖

---

okay that’s the whole manual, bestie — go move that subtree like the main character you are 💅 source/version: git-branchless-move(1) from the General Commands Manual; date: the footer didn’t give us a separate date stamp, so that’s the sign-off vibe 🎀✨