re: Git Workflow: How much change is too much change for one commit for you? VIEW POST

FULL DISCUSSION
 

The first line of my commits describes what the change will be once it's applied, and I try to keep these pretty well defined and under 100 chars or so.

That means there's a nice semantic limit on how much a commit can do, so while a single commit might add 100 media files or even reprettify the whole codebase, I'd split it up if it was doing two things that I couldn't fully describe in two short sentences.

 

This is a good delineation for when a change is ready for commit. If you describe it simply it is probably too much of a change to the codebase for one commit.

code of conduct - report abuse