Manage source code with GitHub

As a developer, the management of the source code is a top priority, imagine that the modification is complete but found that the file is missing, what should I do? With the source control tool, you can help us to view the modified memory and historical modification records of a code file.

As. NET developer, I used Vss,github as source code Manager

1.VSS: Early VS2005 and other code are stored on the VSS, as Microsoft's early source control platform, I believe that many people have used, for its use is also stuck on the surface of the use, not as an administrator to manage it, so did not have a deep understanding of it, One painful experience is that you need to check out a file on your own, but it's not very convenient when someone else wants to change the same file.

2.GitHub: In 2015, just started using git as the source code manager, it is very different from VSS, it has a complete set of code on each computer, the machine can check out and modify the same file, and in the final check-in, choose which piece of code to keep, If there is a conflict in the same row of the same file, you can choose which version of the conflict to keep, this is the most convenient place. The big reason for choosing GitHub is that it's free.

1. Create a GitHub code warehouse

Open www.github.com, create an account (in the case of a company, you should create an organization)

In the, click New Repository to start creating a new warehouse

When creating the warehouse, fill in the project name, here, I take the person as an example, here the code warehouse is public

2. Clone Code Warehouse

The code warehouse is created, where the code warehouse is empty and the code repository needs to be cloned locally.

3. Create and modify files

This part is handled according to the usual process of development.

It should be noted that each time for different development tasks, we will be in the original branch a new version, after the completion of the changes, and then merge the latest changes to the original branch, so that you can freely choose different functions into different environments.

This will ensure that a certain part of the function is actually completed, and then added to a different environment, to facilitate the bug in different environments of rapid repair (before using VSS, there is a method, but it is more difficult to do)

4. Code check-in

Learning website:

Git tutorials-Liaoche's official website

Learn Git | Codecademy

Tools:

Sourcetree

Manage source code with GitHub