PC_Workman / blog
Friday Shipped & Scarred · #1

git push --force Turned 130 Commits Into 1

Always create a backup-YYYYMMDD branch before any risky git operation. 5 seconds. Could save months.

By Marcin Firmuga·2026-03-27·2 min read·Friday Shipped & Scarred #1

Monday morning. My heart literally stopped. I ran git push --force on PC_Workman — and 130 commits became 1. Permanently.

Eight months of build-in-public history: gone. Every proof this wasn't built over a weekend by some "turbo super AI." Vanished. I panicked — searched reflog, old branches, GitHub API endpoints. Nothing.

Then I remembered something I'd done three weeks earlier, almost by accident: I created an archive branch. Not even as a proper backup — just "to keep old files around for reference." I checked it. 90 commits inside. Not perfect — I lost about 40. But 90 is infinitely better than 1.

What actually shipped

The rest of the week became cleanup mode:

What broke me along the way

The lesson, the painful way: always create a backup-YYYYMMDD branch before any risky git operation. "Clean code" has hidden layers you only see when disaster strikes. And Reddit feedback hurts… but it usually makes the project better.

Slowly moving toward v2.0 and the Microsoft Store. 800+ hours, 20 stars, ~90 downloads. But I'm still here. Still shipping. Still scarred.

What's the worst git disaster you've ever survived?

BuildInPublicOpenSourceLessons
This is the project behind the post. PC Workman is a free, open-source Windows system monitor with an offline AI assistant - everything described here is real, shipped code. Download it or read the source.
#2 →Plans Assume Energy I Didn't Have
MF

Marcin Firmuga

Solo developer · HCK_Labs · building PC Workman in public

Every edition is written from that week's real commits. Newest posts premiere on LinkedIn - the archive lives here. More about me: my story.