Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Git for Programmers

You're reading from   Git for Programmers Master Git for effective implementation of version control for your programming projects

Arrow left icon
Product type Paperback
Published in Jun 2021
Publisher Packt
ISBN-13 9781801075732
Length 264 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Jesse Liberty Jesse Liberty
Author Profile Icon Jesse Liberty
Jesse Liberty
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Introduction 2. Creating Your Repository FREE CHAPTER 3. Branching, Places, and GUIs 4. Merging, Pull Requests, and Handling Merge Conflicts 5. Rebasing, Amend, and Cherry-Picking 6. Interactive Rebasing 7. Workflow, Notes, and Tags 8. Aliases 9. Using the Log 10. Important Git Commands and Metadata 11. Finding a Broken Commit: Bisect and Blame 12. Fixing Mistakes 13. Next Steps
14. Other Books You May Enjoy
15. Index

Fixing Mistakes

The most common reaction to making a mistake in Git is to panic. What if you have just lost all your work? Worse, what if you have broken the master branch?

This chapter will review a number of common Git mistakes and how to fix them. The first rule, of course, is stay calm, or as Douglas Adams said, Don't Panic!

The problems we'll review are:

  • You wrote the wrong message in a commit.
  • You forgot to add changed files from your last commit.
  • Problems with the order of commits or their messages.
  • You need to undo changes made in a commit.
  • You misnamed your branch.
  • You committed to the wrong branch.
  • You trashed a file in a previous commit.
  • You messed up the remote by pushing a broken branch.

To see the answers at work, let's mirror Panofy into ErrorsDemo. Here are the steps we'll be doing:

  1. On the remote, create ErrorsDemo and get its URL.
  2. Go to the local branch you want...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime