



It’s a personal choice! There are many, many options out there. Why should you make VS Code your default Git Editor, Diff Tool, or Merge Tool? If you want to see how an edit, diff, or merge looks in VS Code, go to the corresponding section to see screenshots.
