Git for Teams
A User-Centered Approach to Creating Efficient Workflows in Git
Publisher: O'Reilly Media
Final Release Date: August 2015
Pages: 356

You can do more with Git than just build software. This practical guide delivers a unique people-first approach to version control that also explains how using Git as a focal point can help your team work better together. You’ll learn how to plan and pursue a Git workflow that not only ensures that you accomplish project goals, but also fits the immediate needs and future growth of your team.

The first part of the book on structuring workflow is useful for project managers, technical team leads, and CTOs. The second part provides hands-on exercises to help developers gain a better understanding of Git commands.

  • Explore the dynamics of team building
  • Walk through the process of creating and deploying software with Git
  • Structure workflow to influence the way your team collaborates
  • Learn a useful process for conducting code reviews
  • Set up a shared repository and identify specific team members as contributors, consumers, or maintainers
  • Know the why behind the Git commands your teammates use
  • Use branching strategies to separate different approaches to your project
  • Examine popular collaboration platforms: GitHub, Bitbucket, and GitLab
Table of Contents
Product Details
About the Author
Recommended for You
Customer Reviews

REVIEW SNAPSHOT®

by PowerReviews
oreillyGit for Teams
 
3.7

(based on 7 reviews)

Ratings Distribution

  • 5 Stars

     

    (3)

  • 4 Stars

     

    (1)

  • 3 Stars

     

    (1)

  • 2 Stars

     

    (2)

  • 1 Stars

     

    (0)

71%

of respondents would recommend this to a friend.

Pros

  • Easy to understand (5)
  • Helpful examples (5)
  • Well-written (5)
  • Accurate (3)

Cons

  • Too basic (3)

Best Uses

  • Novice (6)
  • Student (6)
  • Intermediate (4)
    • Reviewer Profile:
    • Developer (6), Sys admin (3)

Reviewed by 7 customers

Displaying reviews 1-7

Back to top

(1 of 1 customers found this review helpful)

 
2.0

Many topics discussed. Very little of Git.

By Jascha

from Barcelona

About Me Developer, Sys Admin

Verified Reviewer

Pros

  • Well-written

Cons

  • Not About Git
  • Too basic

Best Uses

    Comments about oreilly Git for Teams:

    Developed by the mastermind behind Linux to support the development of the kernel, Git is every developer's bread and butter. As such, there is plenty of documentation available online, as well hundreds of juicy code snippets ready to save us the day on Stack Overflow. And of course, searching for Git on the Amazon bookstore results in many pages of results. Among them, most of the books introduce the readers to Git, thus covering the basic commands and the architecture that makes it different from other VCS, such as Subversion. Git for Teams is difficult to categorize in this abudance of titles. It's neither an introduction to Git, nor an advanced text presenting lead developers and SCRUM masters how to better integreate Git within their projects. It's something in between, even though slightly more the latter than the former.

    Released during the summer of 2015, and spanning some three hundred pages, Git for Teams presents the reader 12 chapters that cover many different aspects of Git, not all of them purely technical. As stated above, this book is difficult to categorize. Still, both the title and the back cover seem to rule out this being a text that teaches the basics of Git. On the back of the book, indeed, we read that This practical guide ... explains how using Git as a focal point can help your team work better together. The reader should definitely expect a book that shows how Git can be part of each and every step of the life cycle of a project. With real life examples, if possible.

    The book can be hardly split into parts. While not a cookbook, each chapter stands on its own and does not require the previous ones. The first two chapters have little to do with Git. They are mostly focused on the team: how to set it up, chemistry, code of conduct. Software licenses are also taken into the discussion. The third chapter is by far the best of the whole book. It's about branching strategies. Throughout the years, indeed, many open source projects have presented and evolved models that are not broadly used: branch per feature, named branches (aka state branches), and scheduled deployment. Having a solid and consistent strategy often has a strong impact on the project itself, so that, based on the team size and distribution, it's important to pick a good branching strategy. The author presents four approaches in her book. Each is explained and also represented with friendly diagrams meant to give the reader a better overview of the whole process.

    Chapter four gets us back to the first two: it discusses a topic, having a ticketing system, that while interesting, is not really about Git. Git is instead the guest star of the following chapters. Here the reader is presented the very basic Git commands, from cloning up to tracking remote repositories, passing through fetch and pull. Finally, the book ends discussing GitHub, Gitlab and BitBucket.

    Thoughts. I think the title of this book is misleading. As the back cover states, this book should be about getting Git into the daily work flow of our team, not about how to set up a team and teach its members the basics of Git. Title apart, I think that this Git for Teams tries to cover too much terrain, ending up not covering well any of the topics. On the one hand, indeed, there are chapters presenting some of the very basic commands of Git. But just a part of them. If the team knows Git, these are not useful. If the ream does not, these are not enough. On the other hand, chapter three, which presents different branching strategies is not bad per se, but it's all alone, surrounded by another eleven chapters talking about other things.

    I must admit that the book is easy to read, even if there is not a real flow of the information. As stated already, indeed, each chapter stands more or less on its own. The author presents a lot of diagrams and images which are easy to understand and informative. Thumbs up there.

    Tying it all up, I did not like this book. I do not judge the content itself, but the fact that most of it has little to do with Git at all. Too bad chapter 3 was all alone. That is definitely what lead developers and project managers are interested into. Setting up a team and software licenses are interesting topics. But they do not really fit here.

    As usual, you can find more reviews on my personal blog: books.lostinmalloc.com. Feel free to pass by and share your thoughts!

    (2 of 4 customers found this review helpful)

     
    2.0

    Too much of a git manual

    By Jan

    from Berlin, Germany

    About Me Developer

    Pros

    • Easy to understand
    • Helpful examples

    Cons

    • Too basic

    Best Uses

    • Intermediate
    • Novice
    • Student

    Comments about oreilly Git for Teams:

    I expected to get a book on a meta-level, like how can I use git inside an organization, which processes are proven to work in which context and in which way can git help me organize a software development workflow for my specific projects. Also examples from theindustry would be very welcome. I was not interested in command-line examples on git basics - unfortunately they build the major part of the book.

    I enjoyed reading chapters 2 and 3 and recommend them deeply since the author here really focuses on branching models and workflows you can apply and also illustrates their strengths and weaknesses. The rest of the book focuses an command-line examples and explains how to setup accounts on popular platforms like Github. It is unclear to me who really needs that in a book - it is fairly basic and will be outdated very soon. For a reference, I'd recommend the git website or the various refences around the web, e.g. on the Atlassian website. This book does neither better or worse in explaining the fundamentals.

    (0 of 1 customers found this review helpful)

     
    5.0

    A enjoyable and great read.

    By Bernie Monette

    from Toronto, Ontario

    About Me Developer, Educator

    Verified Reviewer

    Pros

    • Accurate
    • Concise
    • Easy to understand
    • Helpful examples
    • Well-written

    Cons

      Best Uses

      • Expert
      • Intermediate
      • Novice
      • Student

      Comments about oreilly Git for Teams:

      Having worked with hundred of teams over the years it was thoroughly enjoyable to read this book. Git is supposed to help! And with Emma's insightful descriptions and down to earth instructions it just might!

      Well worth the read for new and old alike.

      (0 of 2 customers found this review helpful)

       
      4.0

      A worthwhile purchase

      By Jon W

      from Southampton UK

      About Me Developer, Sys Admin

      Verified Buyer

      Pros

      • Accurate
      • Concise
      • Easy to understand
      • Helpful examples
      • Well-written

      Cons

        Best Uses

        • Intermediate
        • Novice
        • Student

        Comments about oreilly Git for Teams:

        Easy to read and accessable. I have been a solo git user for a few years now but needed some insight on best practice and use of git within a team This book gave me that.

        (3 of 5 customers found this review helpful)

         
        5.0

        A fantastic workplace resource on version control

        By Ben

        from Pittsburgh, PA

        About Me Developer, Sys Admin

        Verified Reviewer

        Pros

        • Easy to understand
        • Helpful examples
        • Social And Technical
        • Well-written

        Cons

          Best Uses

          • Intermediate
          • Novice
          • Student

          Comments about oreilly Git for Teams:

          This book is incredible in that it encompasses both the technical and social information necessary to use version control effectively. It's so important to understand good team practices before adding technology to the equation, and the guidance this book provides can help establish deliberate practices where chaos might otherwise reign.

          Instead of throwing you into the deep end of memorizing commands and terms, Git for Teams walks you through the "why" of version control and how to work within a team, so that you approach the technology with understanding. It's not a cut-and-dry git reference book (it's not meant to be), but the material is laid out such that it can actually be used as one (the table of contents is really, really thorough). The technical material is really helpful for the beginner/intermediate level, but the content on working within a team is absolutely helpful (and necessary) for everyone.

          Most importantly, the book makes almost no assumptions about prior knowledge, which is critical for teams where version control might be completely new or not well understood. (Yes, those places do exist!) There are tons of helpful diagrams to go along with the workflows and models, and some of the less-commonly understood topics are even covered, such as rebasing. Overall, I'd recommend this book as required reading for anyone developing software.

          (4 of 6 customers found this review helpful)

           
          5.0

          Great for beginner to novice

          By netskink

          from Durham, NC

          Verified Reviewer

          Pros

            Cons

              Best Uses

              • Novice
              • Student

              Comments about oreilly Git for Teams:

              When I got this book and the associated video, I was already somewhat familiar with git. I've done the basics, clone, pull, push, diff and a small amount of git admin work. I still felt like git was a nice tool and I was only using 10-30% of its capabilities. I bought this book and the video to learn more.

              I find the book and video to be spot on for someone like myself. I haven't finished either the book or video but I find it easy to pick up when I have a question and find what I am looking for.

              I would recommend either of these for someone wanting to come up to speed on git.

              (6 of 12 customers found this review helpful)

               
              3.0

              Not right for me

              By fordsfords

              from Chicago area

              About Me Designer, Developer

              Verified Buyer

              Pros

              • Accurate
              • Easy to understand
              • Helpful examples
              • Well-written

              Cons

              • Too basic

              Best Uses

              • Novice
              • Student

              Comments about oreilly Git for Teams:

              As somebody who has spent 30 years working on teams, this was not the right book for me. I had hoped that it would concentrate most on how to use git in that environment, but instead the first part of the book concentrated on teaching how to orchestrate team-based development. For somebody who is not experienced in team development, I think this would be a much better choice.

              Moving into the more technical parts of the book, I realized that it didn't assume reader familiarity with other source control systems (like CVS, Subversion, etc). This was clearly intentional, and indicative of the intended audience. Once again, this book would be a much better choice for somebody with less experience.

              Given my experiences, the "Pro Git" book is a much better choice for me. But for an inexperienced developer, I would recommend this book.

              Displaying reviews 1-7

              Back to top

               
              Buy 2 Get 1 Free Free Shipping Guarantee
              Buying Options
              Immediate Access - Go Digital what's this?
              Ebook:  $42.99
              Formats:  DAISY, ePub, Mobi, PDF
              Print & Ebook:  $54.99
              Print:  $49.99