Community
Participate
Working Groups
If a gitflow operation stops due to a merge conflict a result dialog should notify the user what happened and give hints how to resolve them. If e.g. "Finish feature" faces a conflict when trying to merge the feature branch since another feature or fix has touched the same line no explicit message tells the user what happened. Compare this with how EGit handles plain merge or rebase conflicts.
I think all finish operations and feature rebase have to be considered in this bug. For feature rebase, I'm already experimenting with a simple message box, but I am not sure if I need to handle more than just MergeStatus.CONFLICTING. Do you think that would be sufficient? Also for the finish operations? Release finish is more difficult to handle because there are two merges. One to develop, and another to master. Conflicts during the merge to master may have to be treated differently, though because in a git flow repository that can only happen if something went wrong in the past, e.g. when somebody committed to master directly.
https://git.eclipse.org/r/#/c/48516/
merged as http://git.eclipse.org/c/egit/egit.git/commit/?id=8d224df9737f3a7d3227f474fbfd38faf23c5fec