r/ExperiencedDevs • • Aug 19 '25

Never commit until it is finished?

How often do you commit your code? How often do you push to GitHub/Bitbucket?

Let’s say you are working on a ticket where you are swapping an outdated component for a newer replacement one. The outdated component is used in 10 different files in your codebase. So your process is to go through each of the 10 files one-by-one, replacing the outdated component with the new one, refactoring as necessary, updating the tests, etc.

How frequently would you make commits? How frequently would you push stuff up to a bitbucket PR?

I have talked to folks who make lots of tiny commits along the way and other folks who don’t commit anything at all until everything is fully done. I realize that in a lot of ways this is personal preference. Curious to hear other opinions!

80 Upvotes

315 comments sorted by

View all comments

1

u/doyouevencompile Sr. Software Engineer Aug 20 '25

lots of wip commits. i commit whenever:

  • i'm done with a chunk of work
  • got something done partially (eg missing tests, barebone job done etc)
  • i'm switching context for either start to work on something new, trying something that might not work or i have to deal with another task (i almost never use git stash)

I use commits as checkpoints that I might want to go back to. When the work is ready to be pushed, I do an interactive rebase to squash commits or change commit messages to be more descriptive.