DEV Community

loading...

Discussion on: Git Workflow: How much change is too much change for one commit for you?

Collapse
zchtodd profile image
zchtodd

Committing and pushing acts partly as a form of backup for me, but when merging to something like a sprint branch I try to squash those commits so that the history is more about features than tiny changes.

Collapse
indietasten profile image
NDTSTN

That's usually what ends up happening to me, when my task is really big and there really aren't good intermediate steps that could warrant an actual commit.

If there are good steps in between, I think there are great benefits to be had from concise and short commits, that explain the reasoning of themselves in their long message. I don't know how many times I've done a git blame to find the commit of some piece of code, and then it was made as a side-task of something completely different, and nobody can explain, why the change was made.