Configuring Gitīefore you can even start using Git there is some really basic config you need to do, which is set your name and email address. Once you get the branch to a level of confidence you can then merge it to the master and delete that branch. This allows you to maintain your master code which you know works.

With Git if you have your code to a working “production” level you can maintain it, but still develop it by adding what Git referrers to as “branches.” So, if you have a bug you need to fix or a feature you want to add you can create a new branch to address a specific scenario. Before I knew it I had a bunch of different files with various levels of complexity, features, and functions. As I was developing a PowerCLI script once I got a version working I would create a new version for the next feature I wanted to add to my code. It’s a way to track changes to your code as you develop it. Git is an SCM, which is Software Configuration Management. Honestly, I had little clue as to what Git was even just a few weeks before writing this article.

So, one thing I really like about Visual Studio Code is it’s native support for Git.

So, first things first – if you don’t already have them installed go get Visual Studio Code and Git, install them both and come back… Also, get yourself a Github account if you don’t already have one. In this post I’ll go through the detailed steps of configuring Visual Studio Code to work with Git and Github to keep track of your code. For me the default color scheme is easy on the eyes when I’m working, the contextual highlights bring my attention to something when it’s not correct, and it integrates with Github out of the box as well, although some assembly is required. I’m using to develop/learn PowerShell, Power CLI, and Python. I’ve fast become a big fan of Visual Studio Code for my ISE (Integrated Software Environment).

Connect github to visual studio