git-branchless-sync(1)

🎀 NAME 🎀

okay bestie, welcome to git-branchless-sync(1) from the General Commands Manual — this is sync, and its whole job is: Move any local commit stacks on top of the main branch. iconic behavior, honestly 💅

---

✨ SYNOPSIS ✨

here's the exact shape of it, no cap:

sync [-p|--pull] [-f|--force-rewrite] [--in-memory] [--on-disk]
[--no-deduplicate-commits] [-m|--merge] [--reparent]
[--debug-dump-rebase-constraints] [--debug-dump-rebase-plan] [--hidden]
[-h|--help] [REVSETS]

---

🦋 DESCRIPTION 🦋

Move any local commit stacks on top of the main branch. that's the vibe, that's the whole assignment 💖

---

🌸 OPTIONS 🌸

• -p, --pull — run git fetch to update remote references before carrying out the sync. little pre-game refresh, yknow? ✨
• -f, --force-rewrite — force moving public commits, even though other people may have access to those commits. bestie, this is a use-with-care situation fr fr 😭
• --in-memory — only attempt to perform an in-memory rebase. if it fails, do not attempt an on-disk rebase. strict little icon 💅
• --on-disk — skip attempting to use an in-memory rebase, and try an on-disk rebase directly. no in-memory warmup, just straight to the disk vibe 🫶
• --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 yeah, it's giving "I said what I said" 💀
• -m, --merge — attempt to resolve merge conflicts, if any. if a merge conflict occurs and this option is not set, the operation is aborted. so either bring the merge energy or know it's gonna stop 🛑
• --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. highkey a "handle with care" moment, bestie ⚠️
• --debug-dump-rebase-constraints — debugging option. print the constraints used to create the rebase plan before executing it. nerd mode: activated 🧚
• --debug-dump-rebase-plan — debugging option. print the rebase plan that will be executed before executing it. another little peek behind the curtain 👑
• --hidden — include hidden commits in the results of evaluating revset expressions. don't leave the hidden cuties out 🙈
• -h, --help — print help. the classic "help me help you" button 💖
• [REVSETS] — the commits whose stacks will be moved on top of the main branch. if no commits are provided, all draft commits will be synced. no revsets? no problem, it's syncing the whole draft situation 🌈

---

okay that's the whole page, bestie 🫶 signed off cute from the General Commands Manual — page git-branchless-sync(1), footer just says sync, and there's no separate version or date printed on this one, so I'm not gonna invent one. periodt 💜