Book Image

Git for Programmers

By : Jesse Liberty
Book Image

Git for Programmers

By: Jesse Liberty

Overview of this book

Whether you’re looking for a book to deepen your understanding of Git or a refresher, this book is the ultimate guide to Git. Git for Programmers comprehensively equips you with actionable insights on advanced Git concepts in an engaging and straightforward way. As you progress through the chapters, you’ll gain expertise (and confidence) on Git with lots of practical use cases. After a quick refresher on git history and installation, you’ll dive straight into the creation and cloning of your repository. You’ll explore Git places, branching, and GUIs to get familiar with the fundamentals. Then you’ll learn how to handle merge conflicts, rebase, amend, interactive rebase, and use the log, as well as explore important Git commands for managing your repository. The troubleshooting part of this Git book will include detailed instructions on how to bisect, blame, and several other problem handling techniques that will complete your newly acquired Git arsenal. By the end of this book, you’ll be using Git with confidence. Saving, sharing, managing files as well as undoing mistakes and basically rewriting history will be a breeze.
Table of Contents (16 chapters)
11
Finding a Broken Commit: Bisect and Blame
13
Next Steps
14
Other Books You May Enjoy
15
Index

log at the command line

There are a large number of flags you can add to log to control its output. In creating the lg alias, we already saw how to use log -–oneline:

Figure 9.9: Using log at the command line

Looking closely, we see that the left column has the short ID, the right column lists the messages associated with each commit, and for both the first and last commits, we also see where the head pointer is; both locally and on origin.

Which files changed?

If you want to know which files were changed in each commit but not see what those changes were, you would use:

git log ––name-only

Here is an excerpt:

Figure 9.10: Using log to see file changes

We see two commits. The first, in Program.cs, has the message Call the add function, and you can also see the full ID, the author, and when this commit was made.

You can of course do the same thing with our lg alias to condense the output:

Figure 9.11: Using...