Git in Practice

By Mike McQuaid

Summary

Git in Practice is a suite of sixty six confirmed concepts that might optimize how you and your staff deal with your improvement tasks. The publication starts off with a short reminder of the center model keep an eye on suggestions you would like whilst utilizing Git and strikes directly to the high-value positive aspects you'll now not have explored but. Then, you are going to dig into cookbook-style options like background visualization, complex branching and rewriting historical past each one offered in a problem-solution-discussion structure. ultimately you will determine the way to use Git to its complete power via configuration, crew workflows, submodules and utilizing GitHub pull requests effectively.

Purchase of the print publication encompasses a unfastened book in PDF, Kindle, and ePub codecs from Manning guides.

About the Technology

Git is a resource regulate approach, yet it is a lot greater than simply that. For groups operating in state-of-the-art agile, non-stop supply environments, Git is a strategic virtue. equipped with a decentralized constitution that is ideal for a dispensed group, Git manages branching, committing, advanced merges, and activity switching with minimum rite so that you can pay attention to your code.

About the Book

Git in Practice is a suite of battle-tested ideas designed to optimize how you and your workforce deal with improvement initiatives. After a short assessment of Git's middle positive aspects, this sensible advisor strikes quick to high-value issues like heritage visualization, complex branching and rewriting, optimized configuration, staff workflows, submodules, and the way to take advantage of GitHub pull requests. Written in an easy-to-follow Problem/Solution/Discussion structure with various diagrams and examples, it skips the speculation and will get correct to the nitty-gritty projects that might remodel how you work.

Written for builders acquainted with model keep watch over and prepared for the great things in Git.

What's Inside

  • Team interplay options and techniques
  • Replacing undesirable behavior with strong practices
  • Juggling advanced configurations
  • Rewriting historical past and catastrophe restoration

About the Author

Mike McQuaid is a software program engineer at GitHub. he is contributed to Qt and the Linux kernel, and he keeps the Git-based Homebrew project.

Table of Contents

    PART 1 advent TO GIT
  1. Local Git
  2. Remote Git
  3. PART 2 GIT ESSENTIALS
  4. Filesystem interactions
  5. History visualization
  6. Advanced branching
  7. Rewriting background and catastrophe recovery
  8. PART three complicated GIT
  9. Personalizing Git
  10. Vendoring dependencies as submodules
  11. Working with Subversion
  12. GitHub pull requests
  13. Hosting a repository
  14. PART four GIT top PRACTICES
  15. Creating a fresh history
  16. Merging vs. rebasing
  17. Recommended workforce workflows

Show description

Quick preview of Git in Practice PDF

Show sample text content

A A GitInPracticeRedux/branches GitInPracticeRedux/branches/inspiration GitInPracticeRedux/branches/inspiration/. gitignore GitInPracticeRedux/branches/inspiration/00-Preface. asciidoc B proposal department GitInPracticeRedux/branches/v0. 1-release/00-Preface. asciidoc C GitInPracticeRedux/tags/v0. 1/00-Preface. asciidoc E Trunk GitInPracticeRedux/trunk/00-Preface. asciidoc GitInPracticeRedux/trunk/01-IntroducingGitInPractice. asciidoc v0. 1release department 162 bankruptcy nine operating with Subversion A GitInPracticeRedux/trunk/02-AdvancedGitInPractice.

This is beneficial in case you desire to merge a department and point out this within the heritage with out eager to contain any of its alterations. for instance, you may use this to merge the result of a failed scan after which delete the experimental department later on. consequently, the test might stay within the background with no being within the present code.  subtree—A converted model of the recursive approach that detects even if the tree constructions are at various degrees and adjusts them if wanted. for instance, if one department had the entire documents within the listing A/B/C and the opposite had the entire related records within the listing A/B, then the subtree process could deal with this 88 bankruptcy five complicated branching case; A/B/C/README.

Should you made a number of commits to the incorrect department, you can’t use git rebase as is to mend this. yet you are able to do so with git rebase --interactive, which you’ll see in method forty four. Let’s examine the reflog back to work out what results the rebase had. directory 6. 7 Rebase of entirety Rebase checkout B # git reflog D 5d4ad83 5d4ad83 a8200e1 88e8b4b 725c33a 4455fa9 3e3c417 ... Reflog output after rebase HEAD@{0}: HEAD@{1}: HEAD@{2}: HEAD@{3}: HEAD@{4}: HEAD@{5}: HEAD@{6}: rebase entire: returning to refs/heads/inspiration rebase: upload bankruptcy 1 idea.

Firstedition. prestige inprogress [book "gitinpractice. firstedition"] prestige = inprogress those may possibly then be retrieved utilizing git config publication. gitinpractice. firstedition . prestige. Git silently ignores any configuration values it doesn’t realize. this permits you to use the Git configuration dossier to shop different worthwhile facts. i take advantage of it to shop configuration info for a few own shell scripts. for instance, I shop my SourceForge username in sourceforge. username so scripts unrelated to Git can run git config sourceforge.

This contains home windows clients, who might want to set up MSYSGit (which presents Git in a Unix shell on Windows). software program development—This ebook assumes a uncomplicated realizing of (and wish to study extra approximately) how model keep watch over is utilized by a staff of software program builders to construct software program tasks. Git or model control—You may still comprehend models, branching, and merging in Git (such as git devote) or one other model keep an eye on procedure (such as Subversion devote, log, replica, change, and merge). GitHub—You can be in a position to entry a loose GitHub account.

Download PDF sample

Rated 4.28 of 5 – based on 17 votes