Using GitHub with Visual Studio 2012 / 2013 / 2015 смотреть онлайн

This video describes specifically the steps involved in getting GitHub to run with Visual Studio without using anything other than what is or will be provided as part of the VS software and supported by Microsoft.

With the tool pack recommended at the very start of the video it should be possible to run this software on any version from 2010 up. I have personally tried it on 2013.

0:02 Introduction.
0:44 Visual Studio Tools for Git.
1:10 Step 1: Create a local folder for your Github repository.
1:35 Step 2: Create a Github Repository.
2:20 Step 3: Show the Team Explorer panel.
2:30 Step 4: Configuring your git settings.
3:35 Issue 1: Inability to use network drives.
4:20 Brief run through of the Team Explorer home panel.
4:40 Step 5: Cloning any Github repository to your local machine.
5:18 Issue 2: Inability to use SSH.
6:15 Step 6: Opening the repository to begin your work.
6:40 Brief summary of everything that happened to this point.
7:15 Step 7: Creating a blank solution and empty web project inside your repository.
7:40 Step 8: Opening the solution and web project.
7:45 Step 9: Adding a simple HTML page.
8:10 Step 10: Running the sample application.
8:30 Brief run through of including / excluding / reviewing changes.
9:17 Step 11: Our first commit.
9:55 Step 12: Getting ready for the first push.
10:36 Brief run through of the effect of the settings from Step 4.
11:30 Step 13: Our first pull / push.
12:20 Brief intro to pull & push best practices. * Always pull before you push. * Only push working code. * Don't break the build.

Encase it's not clear to anyone, "The Build" as referred to in the video means your remote git repository (in this case GitHub) or the place that your team will be pulling from. It's ok to commit broken code to your local repository (if you really have to), but don't push broken code to the remote repository. The reason for this is because everyone on the team will then get a broken copy when they pull and will at best be unable to work on their part until you solve the problems. That can be a major productivity problem even in small teams.