Git Basics: Getting Git Going

February 14, 2022

Welcome back to the Git Commit(ted) to </Dev> Resources series! Today, we will explore getting Git going and reviewing the basics. Git is a free and open-source distributed version control system. It is easy to learn and has a tiny footprint with lightning-fast performance. Git is supported on practically every platform and has built-in GUI tools for committing and browsing. However, users typically choose to interact with Git via the command-line interface (CLI) or a third-party GUI tool. We will explore the two ways I have personally used Git. I first started with the GitHub Desktop client, and then moved to the CLI built-in to VS Code once I fully understood Git operations. We will provide an overview of the Git basics and link to many external resources to help you get started. It's essential to learn how to leverage Git if you plan to contribute to the VMware EUC code repositories, which we will cover in an upcoming blog.

What is Git?

Git is a free and open-source distributed version control system. It is easy to learn and has a tiny footprint with lightning-fast performance.

  • Git is a fast and modern implementation of version control.
  • Git provides a history of content changes.
  • Git facilitates collaborative changes to files.
  • Git is easy to use for any type of knowledge worker.



Learning Git allows you to clone (download) code samples. For example, the ones published by VMware engineers. Git also allows you to make modifications (fixes or enhancements), then submit those changes for approval to be published. We will cover this process in a later blog, but for now, check out these resources to set up and get started with Git.

Get Git Going Resources

Git is free and open-source and is heavily documented. Therefore, I will not be recreating the wheel. I will instead provide a list of helpful resources to help you get started with Git.

Cheat Sheets


Guided Labs, Guides, and Reference Manuals

Visual Differences between CLI and GUI

VS Code (Git CLI)

VS Code ships with a Git source control manager extension; therefore, getting started is pretty straightforward. However, this requires you to fully understand and leverage the Git commands. VS Code provides standard source control UI and workflows for all source control managers, including Git. You will want to start by clicking the Source Control icon in the Activity Bar on the left to get started. This view will allow you to quickly see your Changes, Staged Changes, and Merge Changes. Below, you can see a quick sample of me staging some changes to the EUC Samples GitHub repository. For a complete walkthrough, see VS Code's Git Support documentation.

<p>Description automatically generated

GitHub Desktop (GUI)

GitHub Desktop is one of many third-party Git applications that enable you to interact with GitHub using a visual application rather than the Git command line. The learning curve is far less than learning all of the Git commands. As you can see below, you cannot edit files directly in this GUI (like you can in VS Code). Still, GitHub Desktop does a better job of showing you files that have changed, and allows you to quickly stage and commit them. It's also great at quickly seeing and changing your current branch. It enables you to fetch remote changes to the repository and shows you a history of everyones' changes. Overall, when using a third-party application, you will not have to learn the GUI commands. This is how I started to grasp the required steps and understand branching. Now I have moved on to doing literally everything I need within VS Code. For more information and steps on using GitHub Desktop, see Getting Started with GitHub Desktop.

A screenshot of a computer</p>
<p>Description automatically generated


I hope this Git overview and explanation between leveraging the CLI or third-party application motivates you to get started with cloning and then contributing to samples and repositories. Be sure to subscribe to the Digital Workspace Tech Zone Blog RSS or check back daily to see what we release. By the end of this month, we hope that you are comfortable leveraging code samples, VMware Flings, scripting/coding, and leveraging the EUC APIs to automate your workspace!

You can also follow us on Twitter @EUCTechZone to stay updated on the latest EUC content!


Make sure to check out the other blog posts in our 28-day series:


Filter Tags

Workspace ONE Workspace ONE Access Workspace ONE Intelligence Workspace ONE UEM Blog Technical Overview Intermediate Optimize