Version Control with Git - Cdn.oreilly.com

More documents

Recommendations

Info

Following Files that Moved 380 Keep, But Don’t Track, This File 381 Have You Been Here Before? 382 21. Git and GitHub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Repo for Public Code 385 Creating a GitHub Repository 388 Social Coding on Open Source 390 Watchers 391 News Feed 392 Forks 392 Creating Pull Requests 394 Managing Pull Requests 396 Notifications 398 Finding Users, Projects, and Code 401 Wikis 402 GitHub Pages (Git for Websites) 403 In-Page Code Editor 405 Subversion Bridge 407 Tags Automatically Becoming Archives 408 Organizations 409 REST API 410 Social Coding on Closed Source 411 Eventual Open Sourcing 411 Coding Models 412 GitHub Enterprise 414 GitHub in Sum 416 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 x | Table of Contents
Background CHAPTER 1 Introduction No cautious, creative person starts a project nowadays without a back-up strategy. Because data is ephemeral and can be lost easily—through an errant code change or a catastrophic disk crash, say—it is wise to maintain a living archive of all work. For text and code projects, the back-up strategy typically includes version control, or tracking and managing revisions. Each developer can make several revisions per day, and the ever increasing corpus serves simultaneously as repository, project narrative, communication medium, and team and product management tool. Given its pivotal role, version control is most effective when tailored to the working habits and goals of the project team. A tool that manages and tracks different versions of software or other content is referred to generically as a version control system (VCS), a source code manager (SCM), a revision control system (RCS), and several other permutations of the words “revision,” “version,” “code,” “content,” “control,” “management,” and “system.” Although the authors and users of each tool might debate esoterics, each system addresses the same issue: develop and maintain a repository of content, provide access to historical editions of each datum, and record all changes in a log. In this book, the term version control system (VCS) is used to refer generically to any form of revision control system. This book covers Git, a particularly powerful, flexible, and low-overhead version control tool that makes collaborative development a pleasure. Git was invented by Linus Torvalds to support the development of the Linux® 1 kernel, but it has since proven valuable to a wide range of projects. 1. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. 1
Page 2 and 3: Want to read more? Spreading the kn
Page 4 and 5: Version Control with Git, Second Ed
Page 6 and 7: Configuring an Alias 30 Inquiry 30
Page 8 and 9: Normal Merges 142 Specialty Merges
Page 10 and 11: 14. Patches . . . . . . . . . . . .
Page 14 and 15: The Birth of Git Often, when there
Page 16 and 17: Along with branching comes merging.
Page 18 and 19: Timeline With the stage set, a bit
Page 20: O’Reilly Ebooks—Your bookshelf

Version Control with Git - Cdn.oreilly.com

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?