团队协作秘籍：Git工作流实战指南

需积分: 9 82 浏览量更新于2024-07-20 收藏 7.91MB PDF 举报

"《Git for Teams》是一本专注于团队协作的实用指南，由EmmaJaneHogbinWestby撰写，它以用户为中心的方法探讨如何在IT编程项目中创建高效的流程。该书的ISBN为978-1-491-91118-1，定价为US$49.99/CAN$57.99，旨在帮助读者理解自身项目中的特定需求，并学会如何利用Git来优化团队协作。作者从工作流和角色互动的角度出发，引导读者深入理解Git在实际项目中的作用。通过本书，读者不仅能掌握软件构建的基本技能，还能了解到Git在版本控制中的核心地位如何提升团队协作效率。书中特别强调了Git在规划项目流程、追求目标达成以及适应团队即时需求和未来发展方面的价值。对于项目管理者、技术团队领导和首席技术官来说，第一部分关于工作流结构的内容尤其实用，提供了实用的策略和指导。而第二部分则更注重实践，包含一系列动手操作的练习，帮助开发人员深入理解并熟练运用Git技术。《Git for Teams》不仅是一本技术手册，也是一本团队协作的实战指南，它教会读者如何将Git与实际工作相结合，实现高效的工作流程，从而推动项目的成功实施和团队的整体进步。无论是对于个人开发者还是团队领导者，这都是一本不可或缺的资源。"

This book will help you to educate yourself, to gain that understanding, and to do

that work.

—Mark Atwood

Director of Open Source Engagement,

Hewlett-Packard Company

August 2015

Seattle, WA

xiv | Foreword

Preface

For nearly two decades, I’ve been working on teams of one or more in a distributed

fashion. My first paid job as a web developer was in the mid-’90s. At the time, I main‐

tained versions of my files by simply changing the names to denote a new version. My

workspace was littered with files that had unusual extensions; v4.old-er.bak was an all

too common sight. I wasn’t able to easily track my work. On one project, which was a

particularly challenging one for me, I resorted to the copyediting techniques I used

for my essays: I’d print out the Perl scripts I was working on, and put the pages into a

ring binder. I’d then mark up my scripts with different colors of pen and transcribe

the changes back into my text editor. (I wish I had photos to share.) I tracked versions

by flipping through the binder to find previous versions of the script. I had no idea

how to set up an actual version control system (VCS), but I was obsessive about not

losing good work if a refactoring failed.

When I started working with other developers, either for open source projects or cli‐

ent work, I was never the first developer on the scene and there was always some kind

of version control in place by the time I got there—typically Concurrent Versions

System (CVS). It wasn’t the easiest thing to use, but compared to my ring binder of

changes, it was definitely more scalable for the distributed teams that I worked with.

Very quickly I came to value the commit messages, and the ease of being able to

review the work others were doing. It motivated me to watch others commit their

work to the repository. I didn’t want others to think I was slacking off!

Meanwhile, I’d been teaching web development at a couple of different community

colleges. In 2004, I had my first opportunity to teach version control in a year-long

program designed by Bernie Monette, at Humber College. The class was split into

several groups. In the first semester, the students sketched out a development plan for

a website. In the second semester, the teams were mixed up, and the new teams were

asked to build the site described by the previous team. In the third and final semester,

the groups were shuffled again, and the final task was to do bug fixing and quality

assurance on the built site. Each team was forced to use version control to track their

work. The students, who had no prior programming experience, weren’t thrilled with

having to use version control because they felt it got in the way of doing work. But it

also made it easier because they never accidentally overwrote their classmates’ work.

It taught me a lot about how to motivate people to use a tool that didn’t feel like it was

core to the job at hand.

In the decade since that class, I’ve learned a lot about how to teach version control,

and a lot about best practices in adult education. This book is the culmination of what

I’ve learned about how to work efficiently with others when using version control. I

encourage you throughout the book to do whatever is best for your team. There are

no Git police who will show up at your door and tell you “you’re doing it wrong.”

That said, wherever I can, I explain to you “the Git way” of doing things so that you

have some guidance on where you might want to start with your team, or what you

might want to grow into. Using “common” ways of working will help you onboard

others who’ve previously used similar techniques.

This book won’t be for everyone. This book is for people who love to plan a route,

and then follow the clearly defined road ahead. My hope is that, if nothing else, this

book helps to fill the gaps that have been missing in Git resources to date. It’s not so

much a manual for the software as a manual for how teams collaborate. If your team

of one (or more) finds bits of this book confusing, I hope you’ll let me know

(emma@gitforteams.com); and if you find it useful, I hope you’ll let the world know.

Acknowledgments

Several years ago, in a little bar off the side of a graveyard in Prague, Carl Wiedemann

indulged my questions about Git. Thank you, Carl. Your enthusiasm motivated me to

convert my frustration with Git into resources to help others avoid the painful pro‐

cess I’d experienced when learning Git.

I had the wonderful fortune to work with Joe Shindelar at my first job-job after a dec‐

ade of self-employment. Joe, your passion for excellence has raised the bar for my

own work. I am grateful for your patience and leadership. This book was born out of

the conversations we had about leadership, team structures, and the Git documenta‐

tion we created for the Drupalize.Me team. Thank you.

O’Reilly found the excellent Christophe Portneuve to serve as one of my tech review‐

ers. Christophe, thank you for your patience as I worked through the first few chap‐

ters. Your feedback was invaluable. I am grateful for the conversation we had at Git

Merge, which helped me to clarify the concepts I use in this book—I had lofty goals

of transforming the way people learn Git. I hope this book has become a resource you

will be proud to have been a part of.

Bernie Monette, Martin Poole, Drew McLelland: you gave me a platform to refine my

understanding of version control through your own projects.

xvi | Preface

剩余354页未读，继续阅读

libingchen

粉丝: 29
资源: 263

团队协作秘籍：Git工作流实战指南

使用Git优化团队协作：人本化工作流程指南

Git团队协作指南

团队协作利器：Git 实战

Git for Teams 无水印pdf

Git for Teams (2015)

diagrams:Git for Teams研讨会，会议，视频和书籍中使用的图表的源文件

people:Git for Teams中使用的人员图标的源文件。 帮助我改善代表人的方式！ 拉请求欢迎！

Learn Version Control with Git: A step-by-step course for the complete

Addison.Wesley.Visual.Studio.Team.System.Better.Software.Development.for.Agile.Teams

teams-collab

最新资源

people:Git for Teams中使用的人员图标的源文件。帮助我改善代表人的方式！拉请求欢迎！