A Git Workflow That Works for Solo Projects

Branches, commits, and releases when you are the only committer but still want history you can trust.

Jul 28, 2025•7 min read

Main stays shippable

Even solo, treat `main` as deployable. Use feature branches for risky refactors.

Future you reads logs. A short imperative subject line plus context in the body saves hours.

Tag versions when you show work publicly or ship to users. It is documentation you will actually use.

Learn `reflog` once. It turns panic into a five-minute fix.

Join the discussion — be respectful and constructive.

Loading comments…