Git Commit Message Guidelines Consistent Git commit messages make a project easier to review, maintain, debug, and release. A good commit message should explain what changed, where it changed, and ideally why the change was necessary. This project follows a Conventional Commits-style format. Commit Message Format <type>(<scope>): <short description> Example: feat(invoice): add OCR-based invoice processing […]
