GitHub easy to get started

**

GitHub easy to get started

**

Beginner GitHub, record the procedure. Not well written, welcome to correct me.
You'll find out what GitHub is all about, and it's not much to say here.

1. First of all, of course, login to the GitHub website
https://github.com/
Click the button "Sign up" in the top right corner of the website to register a github account

Fill in the name, email, password and then click "Create an Account" to submit

The second step directly select free items, github we want to use the public warehouse is free, unless you want to use private, you need to pay 7$ each month.

Click "Continue" to complete the registration.

Log in to the mailbox to activate the mailbox, or every time you go to GitHub is a reminder to see the annoying.

2. Create a warehouse (Repository).
Good English can go through the official entry document, click on the Green "let's Get started!" Keys.
Create a new warehouse and click on the green "new Repostory"

Enter the project name, item description, type Select public Warehouse, if "Private" is to pay. Click "Create Repository" to complete the creation.

After the completion will come out the following interface, these command lines for the operation of GitHub is still very useful, I have it recorded in the notes, easy to find later.

Click on the "README" hyperlink to create a readme.md file
(This Readme file is supported in markdown format)
You can edit the readme.md file directly on GitHub, we'll enter some content, and then click on the button "commit changes" to submit the changes.

3. GitHub's backbone and branches
After adding the Readme.md file, our project is not empty.
Back in the project view, we would see familiar interfaces, often seen when downloading code in Daniel's GitHub, except that our project only has one readme file.

I believe that the code version management control experience is aware of the backbone and branch concept, (do not know Baidu Google)
In general, we will create a branch to modify the code, and then merge (merge) to the trunk when the code development is determined or the bug fix is complete.
Currently we have only one trunk for this project, click on the "Branch Master" button to create a branch.
We create a new branch called "Heapmaster_branch".

Once created, enter the branch and the contents are the same as on the trunk:

Click "Readme.md" file, this edit button feel not very easy to find, see:

Click Edit, modify the content and submit,

After successful submission you will find that the content on the Master branch (trunk) is still original, and the content on the "Heapmaster_branch" branch is already new.

The next step is to merge the branches into the trunk and to be continued.

GitHub easy to get started