Your configuration will open in Visual Studio Code. ... Save this answer. ... Show activity on this post. For what I understand, VSCode is not in AppData anymore. So Set the default git editor by executing that command in a command prompt window: More on stackoverflow.com

Main difference: One you click buttons and the other you type words. The visual one literally executes the same commands that you'd type yourself. So if it works for everything you need, then great. But often when doing something slightly more advanced, there isn't a button for it so you need to use the CLI directly. More on reddit.com

Git via a GUI seems easier, because it is easier. If you're working with Git via the CLI, all you have in front of you is an empty command prompt. To do anything, you already need to know which commands exist, how they're used and how the usage syntax works. You need to know the command names, the command's specific options, some commands even have subcommands, these subcommands then also have specific options, etc. If you don't know these things beforehand then it's gonna be really difficult doing anything on the CLI. On the other hand, when working with Git through a GUI, you don't need to remember all of this usage syntax. You have classic interface elements like menus, buttons, input fields, lists, etc. With this, you can kinda "discover" operations that can be done, without prior knowledge of which operations exist. There's no need to remember that the pull command exists; you simply open the "Git" menu, see the "Pull" item and just click on it. All available operations can be found somewhere — you just need to click through the menus. These two different ways of working give the CLI generally a steeper learning curve than the GUI, but it also gives the CLI a higher skill ceiling. Everything you can do via the GUI can also be done on the CLI, but the same is not true the other way around. If a specific GUI doesn't expose an operation, than you you can straight up not use that operation (with that specific GUI). Meanwhile, on the CLI, ALL operations are available to you, you just need to know the name of the command(s). Another downside of GUIs is that it's always different, depending on the editor/IDE. All editors/IDEs implement the VCS integration differently, so for every software, you'll need to re-learn and adjust how to work with it. Granted, that is not a problem if you're only ever working with one editor, but CLI knowledge can pretty much always be used, GUI knowledge not so much. Depending on your typing speed and skills with CLIs & shells in general, it is very likely that after a while you'll be faster on the CLI than you ever were with a GUI. In the end, it's preference what you want to work with. I — personally — pretty much only use the CLI, most of my colleagues work with Android Studio's Git integration, one uses GitHub's desktop app and some work mixed with GUI and CLI. But all of them that primarily use a GUI were required to do some things with the CLI because there just wasn't a way to do something with the GUI. More on reddit.com

Step by step tutorials: https://vscode.github.com/ More on reddit.com