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

Aliases

Aliases they allow you to create shortcuts to git commands. For example, I have the alias st, which stands for status. Thus, I enter:

git st

and it is exactly as if I had entered:

git status

We'll get to more exciting and useful aliases in just a moment, but first let's look at how these are created. To create an alias:

  • Enter git
  • Enter the keyword config
  • Enter the flag --global
  • Enter the keyword alias followed by a period and then the alias itself
  • Enter the command you are aliasing

This sounds more complicated than it is. For example, to create the st alias, I entered:

git config --global alias.st status

Of course, you don't have to use global. Your alternatives are system and local, but personally, I always use global because I'm the only one on this computer and I want it to always be available.

Here is a slightly more complicated alias that allows you to create a branch and...