Git Logic Puzzles: Debug and Recover

Volume two — 120 challenges in reading broken repositories. The commit that vanished after a hard reset. The branch someone force-pushed over. The afternoon’s changes discarded by a command that gave no warning. In almost every case the work is still there; the problem is knowing where to look and which mistakes leave something behind. Covers force pushes, hard resets, rebases over shared history, merge-conflict resolution, ignore rules added too late, stash and tag mistakes, cherry-pick duplicates, and reflog recovery — including the one common command with no undo. Every answer executed against Git 2.43. The asymmetry worth learning: committed work is almost always recoverable, uncommitted work often is not. Most developers have that intuition backwards.