What are some best practices for writing commit messages in GitHub flow?

What are some best practices for writing commit messages in GitHub flow?

When writing commit messages in GitHub flow, 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 'Add feature' or 'Fix bug'.

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

Sure! A good commit message might look like this: 'Add user authentication feature'. In the body, you could explain how it works and any important details.

What should I avoid in commit messages?

Avoid vague messages like 'fix stuff' or 'update'. Also, don't include unnecessary details that don't help others understand the changes.

How long should commit messages be?

Aim for the summary line to be around 50 characters, and if you need to provide more context, keep the body under 72 characters per line.