git-branchless-amend(1)
π NAME π
okay so this is the git-branchless-amend(1) page from the General Commands Manual, and the command is amend β it amends the current HEAD commit. periodt. π
β¨ SYNOPSIS β¨
amend [-f|--force-rewrite] [--in-memory] [--on-disk]
[--no-deduplicate-commits] [-m|--merge] [--reparent]
[--debug-dump-rebase-constraints] [--debug-dump-rebase-plan]
[--untracked] [-h|--help]
πΈ DESCRIPTION πΈ
This command amends the current HEAD commit. Thatβs the whole description, bestie β no extra lore hiding in here. π
π OPTIONS π
-f,--force-rewriteβ Force moving public commits, even though other people may have access to those commits. π¨
bestie, this is the βare you sure???β option β it moves public commits even when other people may have access to them. use your powers responsibly. π
--in-memoryβ Only attempt to perform an in-memory rebase. If it fails, do not attempt an on-disk rebase. π§ β¨--on-diskβ Skip attempting to use an in-memory rebase, and try an on-disk rebase directly. π½--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. π«Ά-m,--mergeβ Attempt to resolve merge conflicts, if any. If a merge conflict occurs and this option is not set, the operation is aborted. π--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. π¦
lowkey a βuse with careβ situation, bestie β especially if those descendants are coming from a far-away branch, 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. πΊοΈ--untracked <UNTRACKED_FILE_STRATEGY>β How should newly encountered, untracked files be handled? π
Possible values:
add: Add all untracked filesdisable: Disable all untracked file checking and processingprompt: Prompt the user about how to handle each untracked fileskip: Skip all untracked files
-h,--helpβ Print help (see a summary with '-h'). π
π thatβs the whole page, bestie! source/version: git-branchless-amend(1) (no separate version number printed here); manual: General Commands Manual; footer title: amend; date: not shown on this copy, so no cap, Iβm not making one up π«Άβ¨
π¦ where this page comes from
- arch rolling: git-branchless 0.11.1-2 Β· Apache-2.0 AND MIT
- nixpkgs unstable: git-branchless 0.11.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms