ek9_git_merge

Reports status and outcome (already-up-to-date, fast-forward, clean-merge or conflict), newSha/previousSha, commitsMerged, changedFiles and conflictFiles; a conflicting merge aborts with the tree restored.

Category: Execution · Compare: git merge / Merge Branch

When to use it

'Merge feature-x into this branch' - one call with branch; dryRun:true predicts the outcome and the conflicting files without merging. Use mode:'merge-commit' to keep the branch visible in the graph, mode:'ff-only' to refuse a real merge.

When not to use it

Details

outcome shares one vocabulary between preview and apply: already-up-to-date / fast-forward / clean-merge / conflict (conflict only in a preview - the real merge aborts it). Apply status: merged / fast-forward / already-up-to-date with dryRun:false; preview status: ready / conflicts / unchanged with dryRun:true (an in-memory merge-tree, git 2.38+). A dirty tree is refused (dirty-tree); a conflicting merge is aborted with treeRestored:true. noFastForward:true is the IDE alias of mode:'merge-commit'.

Arguments

ArgumentTypeRequiredWhat it is
branchstringyesThe local branch to merge into the current branch.
dryRunbooleanPredict the outcome, the changed and the conflicting files without merging. Default false.
messagestringMerge-commit message. Default: git's own.
modestring: auto | merge-commit | ff-onlyDefault auto (fast-forward when possible, else a merge commit); merge-commit always records one (--no-ff); ff-only refuses when a merge commit would be needed.
noFastForwardbooleanIDE alias of mode:'merge-commit'.