From the course: Agile Software Development: Remote Teams

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Atomic commits: One change, one commit

Atomic commits: One change, one commit

From the course: Agile Software Development: Remote Teams

Start my 1-month free trial

Atomic commits: One change, one commit

“

- Once I started working on a distributed team, I started to understand the value of the phrase, one change, one commit, otherwise known as an atomic commit. With an atomic commit, each commit represents a single change. Ideally, this commit is accompanied by a short descriptive title and a longer description. This practice of creating atomic commits with detailed notes enables other people on your team to more easily understand your thought process without requiring a synchronous event. I like to imagine myself leaving a trail of thought breadcrumbs for my future self or other members on my team to follow. They're like little artifacts of my thinking. And just like an archeologist or anthropologist relies on pottery, coins, and written text to understand people from different eras or cultures, leaving a rich repository of small commits can be an immense help on a distributed software team. Here's how Git recommends splitting up commits. They should be small, logical steps…

Contents