-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
1.6.22
-
Severity 2 - Major
Repro
- Merge some branch into the current branch.
- May some files conflicting
- Use some mergetool to get rid of the merge conflicts
=> There is no commit message prepared.
Expected
There is a commit message prepared and I can commit immediately.
I had a look at the .git folder. Git correctly generates the MERGE_MSG file which usually be used by SourceTree in older versions but not in 1.6.22