Beginning Git and GitHub: A Comprehensive Guide to Version Control, Project Management, and Teamwork for the New Developer

I have read a couple of books on git but found them to either too light on details and explanation or went too deep on advanced topics.If like me, you just wanted to get productive with Git (and GitHub) in as little time as possible, this book is the one to get.Positives:1. Clear, concise writing style2. Make use of GitHub early in the book. I found this to be useful because it allowed me to put into practice the git commands quickly. I prefer this approach vs other books where Git and GitHub were treated separately.3. Excellent explanations of each Git commands including the consequence of executing the commands. The author went beyond just explaining "this is how you use this command" to "this is how you use this command AND these are the things that will be changed"4. Included other things beyond Git e.g. how to write a commit message, when and why you should commit, etc. These are not directly related to Git itself but these are useful practical advice. I suppose if you are working in a software team, most of these would have been communicated to you. But since I am working alone, I really appreciated these practical advice and hints.5. Well designed step by step tutorial.This is the book that finally got me to use and appreciate Git and GitHub.

Technically - very good tutorial.Proofreading by a native English speaker would be even better though.

I am learning much from this book. I used git professionally, under the direction of a lead who said "do this, now do that" so gaining a good grasp on how it all works is very helpful as I strike out on my own.That said, the grammar is absolutely hilarious! I have laughed out loud a few times, it's good to read a tech book with some wit which this one does.

I bought this book as I was lost to understand how Git and GitHub work.. Finally now is all much clearer.PROS:1) Great explenation of the subject, best practicies and common mistakes to avoid;2) Clear examples;3) Opportunity to dig in with exercices;4)Funny way of writing!Great Choice

This book is poorly written, poorly edited, and poorly printed. It's disappointing that a once-reputable publisher like Apress would release something so bad. Instead of this book, I recommend you download a free copy of "Pro Git" by Chacon and Straub at git-scm.com, which is getting kind of old now but still MUCH better (and, ironically, was originally published by Apress). If you absolutely need something more up to date and/or printed on paper, check out the latest edition of Ponuthorai's "Version Control with Git".

This book is very, very basic and longwinded IMO. I don't personally know anybody who hasn't heard of revision control but I guess some people haven't. The whole historical run through of RCS's is tedious, and if you want to learn git, why do you care that people used to use subversion, etc?The pictures are blurry to me, and given the cost of the book, that's unacceptable. Also, some of the screenshots would have benefitted from color -- the whole book is black and white so I hope you can interpret various shades of gray.The writing is generally ok, if long-winded in places, but the book should have had a better editor. Page 4:"As you can see, this has the potential to go out of hands very quickly" should be "As you can see, this has the potential to get out of hand very quickly." Most of the time the writing is understandable but, again, for the money, very low quality.I gave it one extra star because for someone who really doesn't know anything about computers other than they store files, this might be an OK book. I'm just not the right audience for it. Bought the O'Reilly Git book and am much happier with it.

The author's terrible English makes this book intolerable! Apress should be embarrassed by this.This author's English is so bad you can almost hear him talking to you in an accent so thick....

I like the pace the author is going through the subject. I haven't used Git in some time, so it's a good review. However, the one complaint I have is that lack of a cohesive project, and the formatting of commands on the screen. The colors used in the authors display detract from what the author is attempting to demonstrate. Other than that, the book was worth it to me.

I knew nothing about GIT and now I have stuff on github, so the book gets the job done.

Version control was very grim to me before reading this book. For me concepts like add, commit push pull pull-request revert have been a black hole for years and I was lost in understanding the whole git process as well. Thank you Mariot

The English is very poor. For example "wildy" is frequently used when the author meant "widely".