What are some best practices for writing commit messages?

What are some best practices for writing commit messages?

When writing commit messages, it's important to be clear and concise. Start with a short summary of the changes, ideally under 50 characters. Follow it with a more detailed explanation if necessary, and use the imperative mood, like 'Fix bug' or 'Add feature'.

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

Sure! A good commit message might look like this: 'Fix user login issue by updating authentication logic.' This clearly states what was done and why.

How long should the detailed explanation be?

The detailed explanation can be as long as needed, but it's best to keep it under 72 characters per line for readability. Aim for clarity and relevance.

Should I include ticket numbers in my commit messages?

Yes, including ticket numbers can be very helpful for tracking changes related to specific issues or features. Just make sure to format them consistently.