GitHub入门指南：协作与版本控制必备

需积分: 10 132 浏览量更新于2024-07-21 3 收藏 25.3MB PDF 举报

"GitHub"是一本由Peter Bell和Brent Beer合著的技术指南，专为软件开发人员提供深入的教程。这本书的出版编号为ISBN:978-1-491-94974-0，定价为24.99美元（美国）和26.99加元（加拿大），旨在帮助读者掌握这一日益重要的技能——熟练运用GitHub进行团队协作。随着GitHub在软件开发领域的飞速普及，它已经成为了项目管理和协作的首选平台。本书适合各种角色阅读，包括项目管理者、利益相关者、团队成员以及刚开始接触GitHub的开发者。无论你是想审查并评论他人正在进行的工作，还是希望参与特定的代码更改，都能在这本书中找到所需的基础知识和实用技巧。书中详细介绍了如何利用GitHub的网页界面，有效地查看项目并与团队成员进行互动。它不仅涵盖了Git这个版本控制系统的基础概念，还深入探讨了GitHub的具体操作方法和最佳实践，帮助读者理解人们为何选择GitHub作为工作和交流的主要工具。对于那些初次接触GitHub的人来说，这本书是一份理想的入门指南，能够快速上手并避免不必要的困惑。无论是编写代码、文档管理，还是非技术性的文本处理，如合同或剧本，GitHub都提供了广泛的应用场景。通过阅读这本书，读者将学会如何充分利用GitHub的功能，提升团队协作效率，从而推动项目的成功实施。 "Introducing GitHub"是一本实用的教程，旨在帮助读者精通这个现代软件开发的核心工具，无论是为了自身职业发展，还是为了推动团队的技术合作，都是一份不可或缺的参考资料。

e ability to undo changes

If you make a mistake, you can go back to a previous point in time to recover an ear‐

lier version of your work.

A complete history of all the changes

If you ever want to see what your project looked like a day, week, month, or year ago,

you can check out a previous version of the project to see exactly what the state of the

files was back then.

Documentation of why changes were made

Often it’s hard to remember why a change was made. With commit messages in Git,

it’s easy to document for future reference why you’re making a change.

e condence to change anything

Because it’s easy to recover a previous version of your project, you can have the confi‐

dence to make any changes you want. If they don’t work out, you can always get back

to an earlier version of your work.

Multiple streams of history

You can create different branches of history to experiment with different changes to

your content or to build out different features independently. You can then merge

those back into the main project history (the master branch) once they’re done, or

delete them if they end up not working out.

Working on a team, you get an even wider range of benefits when using Git to keep

track of your changes. Some of the key benefits of Git when working with a team are:

e ability to resolve conicts

With Git, multiple people can work on the same file at the same time. Usually Git will

be able to merge the changes automatically. If it can’t, it’ll show you what the conflicts

are and will make it easy for you to resolve them.

Independent streams of history

Different people on the project can work on different branches, allowing you to work

on separate features independently and then merge the features when they’re done.

Why Use GitHub?

GitHub is much more than just a place to store your Git repositories. It provides a

number of additional benefits, including the ability to do the following:

Document requirements

Using Issues, you can either document bugs or specify new features that you’d like to

have your team develop.

Collaborate on independent streams of history

Using branches and pull requests, you can collaborate on different branches or fea‐

tures.

2 | Chapter 1: Introduction

Review work in progress

By looking at a list of pull requests, you can see all of the different features that are

currently being worked on, and by clicking any given pull request, you can see the

latest changes as well as all of the discussions about the changes.

See team progress

Skimming the pulse or looking through the commit history allows you to see what the

team has been working on.

Key Concepts

There are a number of key concepts that you’ll need to understand to work effectively

with Git and GitHub. Here is a list of some of the most common terms with a short

description of each and an example of how they might be used in conversation:

Commit

Whenever you save your changes to one or more files to history in Git, you create a

new commit. Example usage: “Let’s commit these changes and push them up to

GitHub.”

Commit message

Every time you make a commit, you need to supply a message that describes why the

change was made. That commit message is invaluable when trying to understand

later why a certain change was implemented. Example usage: “Make sure to include

Susan’s comment about the new SEC guidelines in the commit message.”

Branch

An independent series of commits off to one side that you can use to try out an

experiment or create a new feature. Example usage: “Let’s create a branch to implement

the new search functionality.”

Master branch (master)

Whenever you create a new Git project, there is a default branch created that is called

master. This is the branch that your work should end up on eventually once it’s ready

to push to production. Example usage: “Remember never to commit directly to master.”

Feature (or topic) branch

Whenever you’re building a new piece of functionality, you’ll create a branch to work

on it. That’s called a feature branch. Example usage: “We’ve got way too many feature

branches. Let’s focus on getting one or two of these nished and into production.”

Release branch

If you have a manual QA process or have to support old versions of your software for

your customers, you might need a release branch as a place to make any necessary

fixes or updates. There is no technical difference between a feature or release branch,

but the distinction is useful when talking about a project with your team. Example

usage: “We’ve got to x the security bug on all of our supported release branches.”

Key Concepts | 3

Merge

This is a way to take completed work from one branch and incorporate it into

another branch. Most commonly you’ll merge a feature branch into the master

branch. Example usage: “Great job on the ‘my account’ feature. Could you merge it into

master so we can push it to production?”

Tag

A reference to a specific historic commit. Most often used to document production

releases so you know exactly which versions of the code went into production and

when. Example usage: “Let’s tag this release and push it to production.”

Check out

To go to a different version of the project’s history to see the files as of that point in

time. Most commonly you’ll check out a branch to see all of the work that has been

done on it, but any commit can be checked out. Example usage: “Could you check out

the last release tag? ere’s a bug in production that I need you to replicate and x.”

Pull request

Originally, a pull request was used to request that someone else review the work you

completed on a branch and then merge it into master. Now, pull requests are often

used earlier in the process to start a discussion about a possible feature. Example

usage: “Go create a pull request for the new voting feature so we can see what the rest of

the team thinks about it.”

Issue

GitHub has a feature called Issues that can be used to discuss features, track bugs, or

both. Example usage: “You’re right, the login doesn’t work on an iPhone. Could you cre‐

ate an issue on GitHub documenting the steps to replicate the bug?”

Wiki

Originally developed by Ward Cunningham, wikis are a lightweight way of creating

web pages with simple links between them. GitHub projects often use wikis for docu‐

mentation. Example usage: “Could you add a page to the wiki to explain how to

cong‐

ure the project to run on multiple servers?”

Clone

Often you’ll want to download a copy of a project from GitHub so you can work on it

locally. The process of copying the repository to your computer is called cloning.

Example usage: “Could you clone the repo, x the bug, and then push the x back up to

GitHub later tonight?”

Fork

Sometimes you don’t have the necessary permission to make changes directly to a

project. Perhaps it’s an open source project written by people you don’t know or it’s a

project written by another group at your company that you don’t work with much. If

you want to submit changes to such a project, first you need to make a copy of the

project under your user account on GitHub. That process is called forking the reposi‐

4 | Chapter 1: Introduction

剩余141页未读，继续阅读

sushea

粉丝: 0
资源: 1

GitHub入门指南：协作与版本控制必备

Introducing.GitHub.A.Non-Technical.Guide

Introducing Regular Expressions 无水印pdf

Introducing GitHub A Non-Technical Guide 无水印pdf

github入门 [introducing github]

m3orange.github.io

introducing-golang:介绍 GoLang 幻灯片

GitHub入门指南（第二版）

AI企联系统 Ai企业级系统开心版 uniapp适配 Web+H5+微信小程序+抖音小程序+双端APP

2000d.doc

通过SpringCloud实现微服务：Eureka+Ribbon+Feign+Zuul.zip

最新资源