Technical blog post — anchors the launch. Reusable on your blog, dev.to, Hashnode, r/programming.
Every developer who works on more than one machine has done this dance: you're deep in a refactor on your laptop, you need to leave, and none of it is in a state you'd commit. So you either git stash && git commit -m "wip do not push" and pray, or you just... lose your place and rebuild the context an hour later on the desktop.
Git is brilliant at moving committed history. It has nothing to say about the working state before a commit — and that's exactly the state you're in most of the day.