Atomic Commits

Commit frequently but with purpose. This naturally results in clear and concise—but not necessarily short—commits that make code reviews more efficient. Refer to “Make Atomic Git Commits” and “Atomic Commits” for additional guidance.

Single Unit of Work

Each commit MUST represent one and only one change following the single-responsibility principle.

A commit MAY include edits to multiple files, but these edits MUST share the same reason or purpose.

The commit MUST be able to be reverted without causing side effects.

Level of Effort

A commit SHOULD correspond to one and only one Agile task, representing at most eight (8) hours of sustained effort.