You’ll learn how to:git
译者注:有些GitHub的专有名词没有翻译,不是由于我懒得翻。以本人愚见,这些专有名词就算翻译过来也没有多大意思,原汁原味儿的比较好,实在不清楚能够去金山词霸查查具体含义。程序员
This tutorial teaches you GitHub essentials like repositories, branches, commits, and Pull Requests. You’ll create your own Hello World repository and learn GitHub’s Pull Request workflow(工做流), a popular way to create and review code.github
To complete this tutorial, you need a GitHub.com account and Internet access. You don’t need to know how to code, use the command line, or install Git (the version control software GitHub is built on). // 虽然教程说学习GitHub没必要安装Git,使用命令行操做,可是仍是建议读者稍微熟悉一下Git命令分布式
Tip: Open this guide in a separate browser window (or tab) so you can see it while you complete the steps in the tutorial.ide
Your hello-world
repository can be a place where you store ideas, resources, or even share and discuss things with others.工具
hello-world
. Click Create repository. 学习
译者注:分支和快照是相似的概念,快照指的是在某一时间点的数据状态集合,至关于一种特殊的镜像文件ui
By default your repository has one branch named master
which is considered to be the definitive branch. We use branches to experiment and make edits before committing them to master
.this
master
branch, you’re making a copy, or snapshot, of master
as(与此同时) it was at that point in time. If someone else made changes to the
master
branch while you were working on your branch, you could
pull in(吸取) those updates.
This diagram shows:idea
// 从master分支脱离出来到被merge到master分支以前,feature分支会有一段单独历程
Have you ever saved different versions of a file? Something like:
Branches accomplish similar goals in GitHub repositories. // Branches在GitHub仓库中完成类似的目标---储存一个文件的不一样版本
Here at GitHub, our developers, writers, and designers use branches for keeping bug fixes and feature work separate from our master (production) branch. When a change is ready, they merge their branch into master
. 译者注:master分支保存就是往后要作出来的真正production
译者注:这里的readme-edits分支就是上文中提到的feature分支,属于功能分支,用于增长某个模块功能
These changes will be made to just the README file on your readme-edits branch, so now this branch contains content that’s different from master.
Pull Requests are the heart of collaboration(协同工做的核心) on GitHub. When you open a pull request, you’re proposing your changes and requesting that someone review and pull in your contribution and merge them into their branch. Pull requests sho diffs, or differences, of the content from both branches. The changes, additions, and subtractions are shown in green and red. // pull requests后master分支变化会用不一样颜色显示,增长内容用绿色标识,删除内容用红色表示
As soon as you make a commit, you can open a pull request and start a discussion, even before the code is finished. // commit后就会discussion模块出现
By using GitHub’s @mention system in your pull request message, you can ask for feedback from specific people or teams, whether they’re down the hall or 10 time zones away.
You can even open pull requests in your own repository and merge them yourself. It’s a great way to learn the GitHub Flow before working on larger projects.
Click on the image for a larger version
When you’re done with your message, click Create pull request!
Tip: You can use emoji and drag and drop images and gifs onto comments and Pull Requests.
In this final step, it’s time to bring your changes together – merging your readme-edits branch into the master
branch.
master
.By completing this tutorial, you’ve learned to create a project and make a pull request on GitHub!
Here’s what you accomplished in this tutorial:
Take a look at your GitHub profile and you’ll see your new contribution squares!
If you want to learn more about the power of Pull Requests, we recommend reading the GitHub Flow Guide. You might also visit GitHub Explore and get involved in an Open Source project
Tip: Check out our other Guides and YouTube Channel for more GitHub how-tos.
到此为止,官网上面GitHub入门教程已经介绍完了,相信经过您不屑的努力必定已经学会这些GitHub基础操做。若是想要进一步得学习,推荐GitHub Flow Guide(GitHub流程指南,交互式得操做使得读者更容易理解如何脱离分支、合并分支等概念)。
做为Git系列教程中远程仓库篇---GitHub系列教程的第一篇文章,本文就系统地介绍了GitHub使用者该掌握的基础内容。对系列教程感兴趣的同窗,能够选择订阅我博客,我会在工做之余持续更新,与大伙共同提升(技术层面和英文层面),嘻嘻。