Basic features of GitHub

Copyright belongs to the author.
Commercial reprint please contact the author for authorization, non-commercial reprint please specify the source.
FADEOC Khaos
Links: http://www.zhihu.com/question/20070065/answer/30521531
Source: Know

Basic features of GitHub:

• Repository: You and I do "know the Home", "know the Home" is Repository, that is, the project or "The Future weapons T2 class 425mm magnetic track gun" and so on, how to call you, you just know Repository is a place to put the project on the line. Sometimes there will be repositories, is the meaning of multiple repository.
• Fork: We make "know the home" work separately, you are responsible for the art, I am responsible for the front-end development, but we also need data server master. You got a PHP Daniel, this Daniel quickly took care of the server side, idle to Nothing, looked at my front-end code, a look, "I am, how can this not be semantically?" All is the exclusively <div> ah, in the future do interactive JS also do not engage in dom ... "so this Daniel found in the repository I wrote" zhi.html ", fork a copy, that is, authorized copy.
• After Branch:fork, in Daniel's GitHub appeared a similarly called "Know the Home" repository, but this repository is a replica, only to him, this is his Branch, that is, branch.
• Pull request: Daniel has finished a brand new high-end zhi.html, which points to push request. I accepted, glanced at it, suddenly surprised at the table, "Chinese football-high, is really high!" ”
• Now you understand that GitHub's structure is repository-branch-(get/push) files. You also find that GitHub can compare the similarities and differences of two files, the new ones are marked with green, and the deleted ones are marked in red. Pull request can also be controlled, even can merge branch, this is the team cooperation weapon Ah, really is tall also, preface it? Do you have a heartbeat?

2. Sign up for GitHub and log in.
4. Download the client and log in, the client is responsible for the data on your hard drive interacting with GitHub server data, and then set up the storage directory. In order to show your talent, you decide to name this directory "the father of the gods."
6. Since there are so many foreign open-source projects, we have no autonomy in the domestic truth. It's important to practice this awesome fork feature. Now you've come to Fadeoc/frontend. GitHub, you see this is a user fadeoc called "frontend" repository, you laughed, this guy learning front-end knowledge but 10 days, code a piece of slag, unexpectedly some code only wrote "Potatoes" and "two dog son" several Chinese characters. You click on the fork in the upper right corner, then clone in desktop, save to "father of the Gods", wow! The file is already in your computer, absolutely FREE! +10086!
8. One hours later, you have a FADEOC of the slag code, decided to help him improve, or else he will be finished the project. After you have changed, pull Request, this ah unexpectedly said your code is too slag, do not absorb. You are a bastard! I do it myself, rob you of market share!
10. You click on the upper right corner of your own avatar behind the + number, chose the first new repository, that is, the new repository, and a name, called "FADEOC", and then click on the green button set up in the desktop, pop-up Save box, select "The Father of the gods." So the "father of the Gods" appeared under a "FADEOC" folder.
12. You wrote your own "home page. html" and placed it under the "FADEOC" folder.
14. You open the client, see the client interface in the master Branch (host branch, the name is too cloud) there has been a uncommitted changes, that is, the uncommitted changes, that is, you just wrote "God Dad home. Html." You open the Show button, add "Roll your Ya Fadeoc" in the summary section, in the description (detail description) position is not necessary to write, but you still decided to add "pop your chrysanthemum" four characters. Then select "Commit to your user name".
16. In order to upload this submission to GitHub let the FADEOC see, you click on the client in the upper right corner shows a "+1" of the sync, that is, after a few seconds, sync before the two curve arrow stop rotation, synchronization succeeded, "+1" disappeared, indicating a successful upload of a file.
18. You come to GitHub, refresh your personal page, "FADEOC" This repository appears on the page, tap it, and inside you see "God Daddy home. html".
20. To make the initial purpose of this project more straightforward, you decide to add a Readme.txt, although there is always a Readme.txt in the folder of N-Multiple software that you downloaded previously, you haven't opened one. But in the circle mixed, you have to mix the stinking, so you in the "FADEOC" under a new Readme.txt, it wrote, "FADEOC, yes, that is you, look at my mouth, you a cheap!" ”
22. Also use client commit, then sync, after a few seconds, refresh GitHub, you see another readme.txt. And in the following more than a text display box, which shows the content inside the Readme.txt "FADEOC, yes, that is you, look at my mouth, you a cheap!" "To avoid the awkward situation where the FADEOC don't want to open Readme.txt and don't see your cordial greetings. GitHub is so sweet.
24. You copied this repository address and emailed it to FADEOC.
26. FADEOC is not so easy to be defeated, so he fork your repository, modify the Readme.txt, and then pull request, you see FADEOC New Generation Branch under the Readme.txt was changed to "you are the scum." You rejected the merge request.
28. FADEOC again pull request,readme.txt changed to "Dare not do evil?" ”
30. You are a little bored, how can this fucking not let him pull request, in the future big item n Many strangers rookie pull request is annoying, can not be open source, turn private? You finally found GitHub's upgrade service, and you laughed and turned the repository from public to private. FADEOC will continue to pull request, without your response, he will only gradually be the wrath of revenge of the fire to make sense, but, who cares?

GitHub has more details, and in the process of using it, you'll slowly discover it and learn it slowly. But anyway, now you're going to use the basic features of GitHub.

GitHub's basic features