Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

True but. There's a huge trade-off in time management.

I can spend hours OCDing over my git branch commit history.

-or-

I can spend those hours getting actual work done and squash at the end to clean up the disaster of commits I made along the way so I could easily roll back when needed.





it's also very easy to rewrite commit history in a few seconds.

reply


If I'm rewriting history ... why not just squash?

But also, rewriting history only works if you haven't pushed code and are working as a solo developer.

It doesn't work when the team is working on a feature in a branch and we need to be pushing to run and test deployment via pipelines.

reply


> But also, rewriting history only works if you haven't pushed code and are working as a solo developer.

Weird, works fine in our team. Force with lease allows me to push again and the most common type of branch is per-dev and short lived.

reply




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: