![]() 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? If you want to see how an edit, diff, or merge looks in VS Code, go to the corresponding section to see screenshots. Then, run the command git config -global -e to edit the global config, and add the following: To make VS Code your default "everything", first you need to ensure you can run VS Code from the command-line as outlined in the Prerequisite section. Let's look at the potential benefits of using VS Code as a fully-fledged Git partner, and how you can do it. ![]() Do you use VS Code as your default Git editor, or as your Git diff tool?
0 Comments
Leave a Reply. |