Git

Commits

Grouping

• Group changes into cohesive commits by unit of work: one commit per logical change that could be deployed, reverted, or cherry-picked independently.
• When a diff spans multiple concerns (feature + refactor, fix + test, rename + behavior change), split into separate commits. Stage files selectively with git add <paths>.
• Ask yourself: "if this commit were reverted, would exactly one coherent thing disappear?" If not, split it.

Conventional Commit Format

<type>[scope]: <description>

[body]

[footer]