Almost lost 3 hours of work because I didn't understand git branches

I was learning git basics and made a change on my main branch that broke everything. Took me forever to figure out I should have made a separate branch first for testing. Has anyone else had a git mistake that cost them a bunch of time?

2 comments

2 Comments

grace4191mo ago

12 branches is when it finally clicked for me actually. I used to just work straight on main and hope for the best, but that broke stuff so many times I finally gave up. Did you end up using a branching tool or just the terminal commands?

-1

ellis.victor1mo ago

Used to think branches were just extra steps slowing me down. Then I pushed a half-baked feature straight to main and broke the login for three hours on a Friday afternoon. Switched to a simple branch-per-feature thing with the terminal and it saved my butt more times than I can count. Now I won't push anything unless it's been tested on its own branch first.