Hacker News new | past | comments | ask | show | jobs | submit login

One of the things I like about git is that I can make bad commits and fix them later. If I'm working on one feature and I'm interrupted by another task, I can commit "wip - blah", then check out a different branch and work on that. When I go back, I pick up exactly where I left off, and amend the half-finished commit into something that actually makes sense before pushing it out to the rest of the team.

In the past, I never made those sorts of commits, because I used VCSs in which you couldn't. Instead, I avoided committing by checking out a separate workspace for the new work. That's a lot slower, though, and it's easier to lose uncommitted changes. Committing incomplete, broken work allows you to leverage your VCS to manage even your unfinished code.




"git stash" was created for this purpose


git stash is handy. I tend to forget about stashed code, though, so I only stash stuff if I know I will pop it soon.




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

Search: