Friday Shipped & Scarred #1: The Day git --force Deleted 130 PC Workman Commits (I Got 90 Back)

Friday Shipped & Scarred #1: The Day git --force Deleted 130 Commits (And How I Got 90 Back) First in a weekly series tracking PC_Workman development. The good, the broken, the lessons learned. Monday: My Heart Stopped I ran git push --force on PC_Workman. 130 commits became 1 commit. Eight months of development history disappeared. Not the code. The code was fine. But the story was gone. Every "Fixed memory leak" commit. Every "Rebuilt UI (again)" message. Every timestamp proving this project wasn't slapped together over a weekend. Gone. The Panic First reaction: freeze. Second reaction: check GitHub. One commit. Master branch. That's it. Reflog? Empty. Old branches? None with the history. GitHub API endpoints? Nothing recoverable. I'd read about this happening to others. "Always backup before git surgery" they said. I didn't backup this time... The Recovery: An Accidental Save Then I remembered something. Three weeks ago, I created an archive branch. Not for backup. Just to keep