git-branchless-restack(1)

Hiiii bestie! 💖 You're on the git-branchless-restack(1) page from the General Commands Manual, and this whole page is about restack — the command that fixes up commits abandoned by a previous rewrite operation. It's giving cleanup era, and honestly? We love that for us. Let's go. ✨

🌸 NAME 🌸

restack — Fix up commits abandoned by a previous rewrite operation.

✨ SYNOPSIS ✨

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

💖 DESCRIPTION 💖

Okay so here's the tea: a previous rewrite operation can abandon commits, and restack is the bestie who swoops in to fix them up. That's literally the whole description: Fix up commits abandoned by a previous rewrite operation. Main character cleanup energy, no cap. 🫶

🎀 OPTIONS 🎀

• --hidden — Include hidden commits in the results of evaluating revset expressions. If your revset vibe check needs the hidden girlies, this flag says "bring 'em out." 🙈
• -f, --force-rewrite — Force moving public commits, even though other people may have access to those commits. This is the spicy one: it can move public commits, and other people may have access to those commits. You've been warned by the facts themselves. 😭
• --in-memory — Only attempt to perform an in-memory rebase. If it fails, do not attempt an on-disk rebase. So it's in-memory only, bestie — if that fails, there is no on-disk rebase fallback. 🧚
• --on-disk — Skip attempting to use an in-memory rebase, and try an on-disk rebase directly. Straight to on-disk, no in-memory attempt at all. 💅
• --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. Dedup? Not today. 💀
• -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 it tries to resolve merge conflicts if any, but if a merge conflict happens and you didn't set this? Operation aborted, periodt. 🚩
• --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. That last part is highkey important — use with care, because it may carry along a lot of unintended changes onto the destination. 🫠
• --debug-dump-rebase-constraints — Debugging option. Print the constraints used to create the rebase plan before executing it. 🔍
• --debug-dump-rebase-plan — Debugging option. Print the rebase plan that will be executed before executing it. 🗺️
• -h, --help — Print help. That's it, that's the vibe. ✨
• [REVSETS] (default: draft()) — The IDs of the abandoned commits whose descendants should be restacked. If not provided, all abandoned commits are restacked. So if you don't pass it, literally all abandoned commits get restacked. 👑

---

That's the whole page, bestie. Cute sign-off time: this was the git-branchless-restack(1) / restack manual page from the General Commands Manual, and the footer just gives you restack + git-branchless-restack(1) — no extra source/version or date info here, ngl. Now go fix up those abandoned commits and slay. 💅💖✨