Atomic Commits
OK, so now you can start working on your contribution. As you do so, make sure to follow the old adage: Commit early; commit often. Tightly scoped—also known as atomic—commits are safer commits. With an atomic commit, you easily can see what you’ve changed, because your commits are scoped to a single (usually small) topic, feature, or bug fix. This reduces the risk of contributing unnecessary changes. Atomic commits are also much easier to review afterward and to back out should something go wrong. When you make atomic commits, they affect and touch as little of the project as possible, therefore reducing the potential ripple effects of your changes.
Let’s get metaphorical: Think of your complete contribution as an essay. It’s ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access