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

Clean

From time to time, you'll find that there are untracked files listed in your status. 99% of the time these will be files you created and you'll want them to be tracked, which you do by adding them to the index (as shown previously). There are times, however, when you may find untracked files that you don't want:

Figure 10.15: Untracked files

In this case, we have a couple choices. We can add Untracked.cs to the index or we can get rid of it. To do so, we try git clean:

Figure 10.16: Using clean to remove untracked files (fails)

Because git clean is one of the few truly destructive commands—once called, the untracked files are gone, never to be seen again—Git comes back with the snarky reply that it is "refusing to clean." To actually clean, Git requires that you tell it you really mean it by using the -f (force) flag:

Figure 10.17: Using clean as above, but with the force flag (succeeds)

The -f flag...