Or you could re-install and ensure that the it happens through the wizard (there is an option).
If you did not see some help output, it means you currently can’t run VS Code from the command-line. To test this, run the command code -help from the command line. It is possible that this wasn’t done as part of your installation. You need to ensure you can run VS Code from the command-line before you can make it a default Editor, Diff Tool, or Merge Tool. If I can do it all in my code editor, I have a consistent colour theme without further configuration.Some merge conflicts are demanding, I like to jump to source files to get the complete picture, I can use familiar shortcuts if I can do it in VS Code.For diffing, I prefer viewing it in a GUI-based editor.I would prefer to switch to another tab of my code editor rather than a separate window. I prefer less switching between applications generally.I haven’t used some of the Linux command-line tools associated with Git such as Nano enough to get the necessary muscle memory, I forget the commands! ? It can be a flow-buster.If I am executing an interactive git command that requires input from me to edit and review a chunk of text, I would prefer to stay in my code editor and stay in the same mental mode.Here are the situations where I have encountered friction or have an alternate preference: In a sentence, I prefer to do as much as I can in my code editor. I’ll explain my decision and maybe it will give your some insight in to understanding what works best for you. Above all else, your tools should complement your workflow and not impede you. 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? It's not the most beautiful or most actively maintained or most powerful Git UI, but it covers everything a beginner could want to do and more and it has the option of showing you the command line commands that are run when you take an action via the UI, making it a valuable tool not only for starting to work with Git but also for getting to learn the Git command line.If you want to see how an edit, diff, or merge looks in VS Code, go to the corresponding section to see screenshots. I encourage beginners to try out Sourcetree. I don't think an app would last very long of it was showing unreliable information. Re Git UIs being unreliable: I know people who don't like Git UIs but I haven't heard that particular complaint. For example VSCode turns Git's notes into buttons, and Sublime Text has a plugin that adds keyboard shortcuts for selecting one version or the other. Popular code editor apps have features or plugins to help that along, which I suppose could be considered conflict resolution helper tools. You can then edit the file until it looks the way it should look, save, and follow the instructions that were logged to the terminal. In addition conflict resolution is something Git does a nice job of getting the user with all on its own: if there's a conflict, an explanation is logged to the command line, and notes are added to the conflicted file explaining "this is version 1", "this is version 2". If you have a conflict, run mergetool with the command git mergetool. Git comes with mergetool, a command-line based conflict resolution tool. I think you can start with the conflict resolution tools Git provides for you.