1. Background
If there's conflicts in the work tree, GG+ shows a header "Rebase Conflict (0/1 Resolved)" and a list of conflicting files.
When you click on one it opens the merge editor. I don't like the merge editor and instead prefer to edit the file manually with the merge.conflictStyle diff3 config.
VSCode has an option git.mergeEditor: boolean that controls the action when opening conflicting files from the native source view true => opens in the new merge editor false => opens the file in a normal text editor.
2. Proposed Solution
Please check and follow the git.mergeEditor preference when opening conflicted files from that list.
3. Affected Area
Check all that apply.
4. Alternatives or References
Currently, this view of GG+ doesn't have much over the native file list in source control, so I'll continue using that.
The native functionality is fairly basic though, and e.g. lacks a git rebase --abort button that GG+ provides. I think there's plenty of room to make GG+ more useful than the native interface.
1. Background
If there's conflicts in the work tree, GG+ shows a header "Rebase Conflict (0/1 Resolved)" and a list of conflicting files.
When you click on one it opens the merge editor. I don't like the merge editor and instead prefer to edit the file manually with the
merge.conflictStyle diff3config.VSCode has an option
git.mergeEditor: booleanthat controls the action when opening conflicting files from the native source viewtrue=> opens in the new merge editorfalse=> opens the file in a normal text editor.2. Proposed Solution
Please check and follow the
git.mergeEditorpreference when opening conflicted files from that list.3. Affected Area
Check all that apply.
4. Alternatives or References
Currently, this view of GG+ doesn't have much over the native file list in source control, so I'll continue using that.
The native functionality is fairly basic though, and e.g. lacks a
git rebase --abortbutton that GG+ provides. I think there's plenty of room to make GG+ more useful than the native interface.