Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include Actual 3-way Merging in the 3-way Merge Editor #159821

Closed
enjibby opened this issue Sep 2, 2022 · 3 comments
Closed

Include Actual 3-way Merging in the 3-way Merge Editor #159821

enjibby opened this issue Sep 2, 2022 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@enjibby
Copy link

enjibby commented Sep 2, 2022

I have long-used git config --global merge.conflictStyle diff3 as an excellent way to see the "motivation" behind each side of a conflict. This includes a copy of the original code before either of the changes were made to make the changes more obvious.

image

When the new Git Merge Editor was unexpectedly turned on by default, I lost the ability to see this "parent of..." section until I eventually found a way to return to the old conflict resolution view that I had grown to rely on.

If git is set to merge.conflictStyle diff3 and an additional setting in vscode is enabled, could we please have either:

  1. some sort of highlighting that shows us how each side of the merge differs from the "parent of..." instead of each other?
  2. a 4th pane showing the "parent of..." view?
@yume-chan
Copy link
Contributor

Duplicate of #155277

@gjsjohnmurray
Copy link
Contributor

/duplicate - thanks @yume-chan

@vscodenpa vscodenpa added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 2, 2022
@vscodenpa
Copy link

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Sep 2, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Oct 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

5 participants