Git with VS Code for Mac: Part 3 – Configuring Git and VS Code

In my previous post, I discussed how to install both Git and Microsoft Visual Studio Code on MacOS. This is the third and final part of my three-part blog series on integrating Git with VS Code for MacOS. In this post, I’ll cover how to configure Git and Microsoft Visual Studio Code to work together to synchronize with GitHub.

Git with VS Code for MacOS blog series:

• Part 1 – Installing Microsoft PowerShell and VMware PowerCLI
• Part 2 – Installing Git and VS Code
• Part 3 – Configuring Git and VS Code (this post)

Advertisement

Git with VS Code for Mac: Part 2 – Installing Git and VS Code

In my previous post, I discussed how to install Microsoft PowerShell and VMware PowerCLI on MacOS. This is the second part of my three-part blog series on configuring Git with VS Code for MacOS. In this post, I’ll cover how to download and install both Git and Microsoft Visual Studio Code.

Git with VS Code for MacOS:

• Part 1 – Installing Microsoft PowerShell and VMware PowerCLI
• Part 2 – Installing Git and VS Code (this post)
• Part 3 – Configuring Git and VS Code

Git with VS Code for Mac: Part 1 – Installing PowerShell and VMware PowerCLI

Ever since I wrote my blog series Git Integration with VS Code, I’ve been wanting to do a similar series of posts for those of us who primarily run MacOS. While a lot of the similar concepts from that series apply, I still wanted to go through the process step-by-step for those who may be completely new to this concept.

As a VMware administrator, I want the ability to write or update my PowerCLI scripts on GitHub from whatever system I have with me. Sometimes it may be my corporate-issued Windows device, and other times it might be my personal MacBook Pro. Regardless, I want to be able to synchronize my work on both systems and platforms. Now that both Microsoft PowerShell and Visual Studio Code are available on both platforms, I can work on either platform at any time and pick right up where I may have left off.

Git Integration with VS Code: Part 5 – Syncing with GitHub

For the fifth and final portion of my Git Integration with VS Code blog series, this post focuses on Synchronizing Content with GitHub. Previously in Part 4, we configured Visual Studio Code to establish a connection and download content from GitHub. In this post, I wanted to focus on staging, committing, and pushing content back up to GitHub.

Git Integration with VS Code: Part 4 – Configuring Visual Studio Code

Now that PowerShell has been upgraded, and we installed both Git and VS Code, let’s go ahead and configure our environment for synchronization with GitHub. For me, this part was really the meat and potatoes of getting VS Code to integrate with Git and GitHub.

Installing the PowerShell Module

Now that VS Code is installed, let’s install the PowerShell Module so that it can properly understand PowerShell scripts and *.ps1 files.

VS Code: Fixing Git Certificate Issues

Earlier this year, I started messing around with VS Code as a to see how it compared to the default PowerShell IDE that I’ve been using previously. It’s definitely grown on me, and I’ve been drawn to this whole concept of Git integration, not only for accessing my scripts amongst a variety of systems, but also to collaborate with my colleagues on our company’s internal GitLab site.

In trying to set up Git integration with this internal GitLab site, I kept getting a certificate error that stated: “Unable to get local issuer certificate.” Some of my colleagues didn’t seem to have this issue, and I had followed the same steps as they did during the configuration piece. We looked through a few different configurations and compared settings, but nothing was really jumping out at us.