On the use of GitHub client and team collaboration

First of all: if you think small write general like, then you meditate on the small part is slag, I believe you will be better.

--------------------------------------------------------------------------------------------------------------- ----

"Go to the chase."

Here, I believe that the initial GitHub Little White may ask what GitHub is, what it does, and so, the small part found an authoritative explanation:

   can host various git Library and provide a web interface, but with other like sourceforge or google Code This service is different, github is the simplicity of branching from another project. Contributing code to a project is simple: first click on the project site's "fork " button, and then check out the code and add the changes to the code base you just separated, Finally, the "github called code player .

Simply said is a project hosting platform, this platform allows you to discuss, source sharing, teamwork and a series of operations, I believe if you know her, you may fall in love with her, saying that GitHub is foreign, or a ... (This omission, you know), this site is very practical, I believe that through the following introduction you will understand

--------------------------------------------------------------------------------------------------------------- --------------

1. Download and install

  : https://github.com/

   At the bottom of the homepage you will see the download link, download for a setup.exe file, when installed, github will download the full version for you, but ... The pit dad thing came, download the full version of the time is very slow, then let the small part of the crazy death, but, and so on, maybe it is my Yan value is too low, cause my download slow is also possible ah ~~

The interface is very concise, is not feel particularly tall, but, looking at such a concise page, the small part of the beginning to see a bit of a mask, What this is, how I operate, completely puzzled, mygod .

2. Create a first Hello project

how so ugly ~ ~ , create for the creation of the project, created after the completion of the approximate length of this:

Those two files ~ ~, is the software automatically created, seemingly recorded items of some information bar

We first add a file in the Hello project hello.txt, after the creation is done, the interface is this paper:

Now you will find a uncommitted changesthat indicates that there are uncommitted changes in your project, which we submit here, and add a description

After submission:

This means that our project has not been published, now we do not publish, we have modified the Hello file, we found that the interface is such a child:

(-: To indicate that we have not submitted the changes)

When we submitted it, we became like this:

Tips:revert After the addition of your project directory will disappear, is not it feel very magical, this is GitHub version control, control every version to achieve the requirements of use

----------------------------------------------------------------------------------------------------------- ----------------------

Now we commit the project:

After submission : Publish Repository----->>>sync, meaning that you can update a remote warehouse project with only a few points of Sync per change

Now, you can see our Hello project in the website:

3. Branching and merging

Branching and merging is a highlight of GitHub , branching: Creating branch nodes; Merging: that is, merging nodes; there is a primitive knowledge in this : (http://gitbeijing.com/simple _branching.html), this link tells the principle of the branch, I think, the small part is very rubbish, rather look at a cow people write the explanation of the site, branch we can be used to test the new features, this new branch will not change the default branch of the code, So we can rest assured that this is a better basis for teamwork, the branch code feels great, so we can merge, don't feel very tall on the look

...... (Omit n -word principle text here)

3-1: Create a branch

Below we use a small function to reflect the role of the branch:

The current branch is idea, and we create a YY file in the directory:

Files under the directory:

When we switch to the Master node:

Just now that the document is gone, is not the feeling is very magical kind of paper, the small part also think so, La La la ~

3-2: Merging Branches

By clicking on the button, pop up the above option and we can do two versions of the merge

So we can see the merged content under the Master node, so the idea node just now can be deleted, and the delete operation is done at the manager .

We saw the file we just added by looking at the GitHub website:

We see our previous history operation under the commit option:

4. Basic introduction to theGitHub website

use of 5.issues : http://gitbeijing.com/issues.html

use of 6.Pull requests : http://gitbeijing.com/github_flow.html

7. Team Collaboration:

When a project's internal team is collaborating, you must add the specified members to the project, which can publish permissions to the project:

After adding a member, each time you submit a project, your members can create a node for publishing, and your GitHub will have dynamic hints

--------------------------------------------------------------------------------------------------------------- -------

Words always feel small write very stained, so, small make up to everyone to share a few links, these links, I believe that you can understand the use of GitHub

1. Move into GitHub on the Web : http://www.imooc.com/learn/390

2.git Beijing : http://gitbeijing.com/

3. Understand GitHub flow: http://gitbeijing.com/flow/

4. The production of a free static website : https://pages.github.com/

5. Baidu Encyclopedia -github: http://baike.baidu.com/link?url=7hShPF6l133UwPZS3Rypu3cPosUrxp4AdZUAmyeJ-in-F_ Enbe0hoewaezzocxbsyfgxiswuhypbwexr4fjdyk

These few sites, I am sure will make you familiar and skilled in using GitHub 's

On the use of GitHub client and team collaboration