It is therefore comparable to peer-to-peer technology in which there is technically no server – when compared to traditional client/server architecture. If you don’t have time to read it, here is short summary: The post explains that Git is a Distributed Version Control System in which all nodes of the distributed system run a full copy of the Git repository. Consequently all the instructions are also valid for other Git repositories whether they are web-hosted (such as Bitbucket – another popular code sharing platform) or on premise (such as Git installed on a rerver or a TFS 2013 Git repository).įor more information about Git, you can read my previous post: Git TFS Visual Studio Integration where I compare different type of repositories (Centralized vs Distributed), introduce Git and explain how Git integrates with Visual Studio and TFS. Note that while this tutorial is about GitHub, the Visual Studio integration part is identical regardless of the actual Git repository used. In this post, I will explain how to create a GitHub repository and how to use it with Visual Studio. This is why it is important to know about Git and more importantly to know how to use it. I chose GitHub as Git repository because GitHub is becoming the leader repository for people to share code and collaborate. A subscription to GitHub is free for public repositories and several paid plans exist for private repositories. A Git repository is an implementation of a Distributed Version Control System. For those, the first thing to say is that GitHub ( is a web-hosted Git repository. This article is aimed at beginners who are new to GitHub and so also probably new to Git repositories. Visual Studio GitHub integration tutorial – Getting Started with Git.

Visual studio github tutorial