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

amend - Amend the current HEAD commit

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]

Amend the current HEAD commit

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
How should newly encountered, untracked files be handled?

Possible values:

  • add: Add all untracked files
  • disable: Disable all untracked file checking and processing
  • prompt: Prompt the user about how to handle each untracked file
  • skip: Skip all untracked files
Print help (see a summary with '-h')
amend