1. General
  2. RFE (Request for Enhancement)
+5
Completed

Support octopus-merge strategy [SG-17545]

Sync 8 years ago • updated 1 month ago • 3

When collecting patches from several branches, an octopus-merge makes it clear that this particular merge-commit is meant to combine several branches (rather than merging or cherry-picking them one by one). 

Currently, SmartGit does not support this, although the Log does support displaying the result of an octopus merge.  We still need to merge via command line first.

One simple implementation is to check for conflicts first (whether literal or logical conflict), and disallow it if any conflicts exist.  i.e. restrict it to a clean merges only.

Missing Git feature
GOOD, I'M SATISFIED
Satisfaction mark
Satisfaction mark by Sync 1 month ago
Colin Richardson 8 years ago

To get around the conflict problem, you could:


  1. Allow you to merge multiple branches to working tree. (Currently only 1 is allowed at a time)

    This would give you the opportunity to resolve conflicts.
  2. Keep track of all the branches that have been merged from.
  3. On the final commit screen, you could still have your "Merge commit" or "Simple commit" dialog, but rather than say multiple parents, could have it count the parents out.
Completed
Marc Strapetz 1 month ago

Will be present for 25.1.058 Preview build.

+1
Sync 1 month ago

Nice to see an old request being revived. Thank you!

Gave it a shot and it works great.  Being a Graph person, I did initially tried to do it from the [Graph] pane by cmd+clicking the commits to merge, but it's fine if it's only limited to the [Branches] pane.

    Customer support service by UserEcho