You're reading from Mastering Git Attain expert-level proficiency with Git by mastering distributed version control features

Product type Paperback

Published in Aug 2024

Publisher Packt

ISBN-13 9781835086070

Length 444 pages

Edition 2nd Edition

Tools

Git

Concepts

DevOps

Author (1):

Jakub Narębski

View More author details

Table of Contents (21) Chapters

Preface

1. Part 1 - Exploring Project History and Managing Your Own Work

2. Chapter 1: Git Basics in Practice FREE CHAPTER

3. Chapter 2: Developing with Git

4. Chapter 3: Managing Your Worktrees

5. Chapter 4: Exploring Project History

6. Chapter 5: Searching Through the Repository

7. Part 2 - Working with Other Developers

8. Chapter 6: Collaborative Development with Git

9. Chapter 7: Publishing Your Changes

10. Chapter 8: Advanced Branching Techniques

11. Chapter 9: Merging Changes Together

12. Chapter 10: Keeping History Clean

13. Part 3 - Managing, Configuring, and Extending Git

14. Chapter 11: Managing Subprojects

15. Chapter 12: Managing Large Repositories

16. Chapter 13: Customizing and Extending Git

17. Chapter 14: Git Administration

18. Chapter 15: Git Best Practices

19. Index

Why subscribe?

20. Other Books You May Enjoy

Data recovery and troubleshooting

It is almost impossible to never make any mistakes. This applies also to using Git. The knowledge presented in this book, and your experience with using Git, should help to reduce the number of mistakes. Note that Git tries quite hard not to help you avoid losing your work; many mistakes are recoverable. The next subsection will explain how you can try to recover from an error.

Recovering a lost commit

It may happen that you accidentally lost a commit. Perhaps you force-deleted an incorrect branch that you were going to work on, you rewound the branch to an incorrect place, or you were on an incorrect branch while starting an operation. Assuming something like this happened, is there any way to get your commits back and undo the mistake?

Because Git does not delete objects immediately and keeps them for a while, only deleting them if they are unreachable during the garbage collection phase, the commit you lost will be there; you just need...