Git best practices for commit message

Certainly! Writing a good commit message is essential for maintaining a clean and understandable version history.

The Anatomy of a Good Commit Message

Short, Descriptive Title (50 characters or less)

A more detailed explanation of the changes in the commit.
This can span multiple lines and should provide context
and background information as needed.

- Bullet points can be used to list specific changes or
  features added or removed.
- Be concise but informative.
- Mention relevant issues or references if applicable.

Fixes #

Here are some guidelines for creating effective commit messages:

Short Title: Keep the title concise and to the point. It should be under 50 characters and summarize the essence of the commit.

Detailed Explanation: In the body of the message, provide a more detailed explanation of what the commit does, why it's necessary, and any background information that might be helpful. Use multiple lines if needed.

Bullet Points: You can use bullet points to list specific changes, features added, or bugs fixed in the commit. This helps make the changes more understandable.

Reference Issues: If your commit is related to a specific issue or task, reference it using the "Fixes #1234" or "Closes #5678" format. This helps with issue tracking and integration with project management tools.

Be Consistent: Maintain a consistent style and format for your commit messages across your project or team to ensure clarity and readability.

Real-Life Examples 
Here are a few important short titles that I use regularly.

// Use past tense for commit message.
1. feat - new feature
2. fix - bug fix
3. docs - changes in documentation
4. style - everything related to styling
5. refactor - code changes that neither fixes a bug or add new features
6. test - everything related to testing
7. chore - updating build task, package manager configs etc..

You can come up with your own pattern which suits your team or project. 

In summary, Git commit messages are crucial for collaborative software development. By following best practices, you can create a clear and informative project history that enhances your development workflow and teamwork. Happy coding!