git-branchless-split(1) General Commands Manual git-branchless-split(1)

split - Split commits

split [-b|--before] [-d|--detach] [-D|--discard] [--hidden] [-f|--force-rewrite] [--in-memory] [--on-disk] [--no-deduplicate-commits] [-m|--merge] [--reparent] [--debug-dump-rebase-constraints] [--debug-dump-rebase-plan] [-h|--help] <REVSET> <FILES>

Split commits

Insert the extracted commit before (as a parent of) the split commit
Restack any descendents onto the split commit, not the extracted commit
After extracting the changes, don't recommit them
Include hidden commits in the results of evaluating revset expressions
Force moving public commits, even though other people may have access to those commits
Only attempt to perform an in-memory rebase. If it fails, do not attempt an on-disk rebase
Skip attempting to use an in-memory rebase, and try an on-disk rebase directly
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
Attempt to resolve merge conflicts, if any. If a merge conflict occurs and this option is not set, the operation is aborted
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
Debugging option. Print the constraints used to create the rebase plan before executing it
Debugging option. Print the rebase plan that will be executed before executing it
Print help
<REVSET>
Commit to split. If a revset is given, it must resolve to a single commit
<FILES>
Files to extract from the commit
split