What are some best practices for writing git commit messages?

What are some best practices for writing git commit messages?

When writing git commit messages, it's important to be clear and concise. Here are some best practices:

1. Use the imperative mood (e.g., 'Fix bug' instead of 'Fixed bug').
2. Keep the subject line under 50 characters.
3. Provide a detailed description if necessary, explaining the 'why' behind the changes.

Can you give me an example of a good commit message?

Sure! A good commit message might look like this:

Fix user login issue

This commit resolves a bug that prevented users from logging in due to an incorrect API endpoint.

What should I avoid in commit messages?

Avoid vague messages like 'fixed stuff' or 'changes made.' Also, steer clear of including too much detail in the subject line; keep it focused.

How often should I commit my changes?

It's best to commit changes frequently, ideally after completing a logical unit of work. This helps keep your history clean and makes it easier to track changes.