The Perfect Commit (2022)
a year ago
- #productivity
- #software-development
- #git
- The Perfect Commit includes implementation, tests, documentation, and a link to an issue.
- Each commit should be a single, focused change for easier review and future understanding.
- Tests increase productivity by ensuring changes don't break existing features.
- Documentation should live in the same repository as the code for trust and versioning.
- Issue threads provide unlimited space for background, decisions, and links related to the change.
- Not every commit needs to be perfect; exceptions include typo fixes and minor bug fixes.
- Exploratory or experimental code can be written in branches and later squashed into a perfect commit.