Commit Conventions

[MFarabi619]

Conventional Commits

Benefits of Conventional Commits:

1. Automated SemVer: Conventional commits can be parsed by tools to automatically determine the type of changes in the codebase. This can then be used to automatically update the semantic version of the software and generate accurate release notes.

2. Improved Readability: The commit log becomes more readable and easy to understand. Each commit clearly describes the type of change, making it easier to spot breaking changes or new features.

3. Easier Navigation: It's easier to navigate through the history of the project by looking for certain types of commits (fixes, features, etc.) instead of trying to understand what each commit does by reading the title or the diff.

4. Reduced Mental Overhead: They provide developers a clear structure to follow, reducing the mental effort needed to document changes in the codebase.

5. Collaboration and Communication: Conventional commits enforce a standard that all team members follow. This leads to better collaboration and communication among team members, especially in larger projects. It also helps new team members understand the project history more easily.

6. Automated CHANGELOG Generation: Tools like standard-version or semantic-release use the commit messages to automatically generate a CHANGELOG file, saving manual effort and reducing errors.

By using conventional commits, a project's maintainers and contributors can communicate more effectively about what a commit does, making the development process smoother and more manageable.