Crafting Commits with Finesse: The 7 Rules for Exceptional Git Commit Messages
Published: 2023-10-13 14:14:54

Hey there, fellow Git enthusiasts! 🚀 It's time to talk about those tiny, but oh-so-important messages we send to the Git repository: commit messages! 📝 


![Minions get started](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/13xqssu7o5g3jmwarclk.gif)




Git commits are like little notes you leave for yourself and your fellow developers, and following these seven rules will ensure those notes are not just informative but also look pretty darn good. So, without further ado, let's dive into the seven rules of a great Git commit message. 

**1: Separate subject from body with a blank line**

Imagine if you received a letter with no paragraphs or spaces between sentences. It would be a confusing, unreadable mess. In the same way, your Git commit messages should have a clear separation between the subject and the body. It's like giving your message room to breathe and be understood.

**2: Limit the subject line to 50 characters**

Think of your commit message as a tweet – you've got 280 characters, but you should aim to say what you need to say in the first 50. This keeps it concise and easily scannable, so your fellow developers know what's up at a glance.

**3: Capitalize the subject line**

This is basic grammar, but it's easy to forget. Capitalize your subject line! It's like giving your message the respect it deserves, plus it looks more professional.

**4: Do not end the subject line with a period**

Commit messages are not full sentences. They're like newspaper headlines or bullet points. So, save that period for the end of your sentences in the body of the message. It just looks cleaner that way.

**5: Use the imperative mood in the subject line**

Now, this rule might sound a bit fancy, but it's not. The imperative mood means you should use a command or request. Instead of saying "I fixed the bug," say "Fix the bug." It's a subtle but effective way to make your commit message feel like an instruction rather than a statement.

**6: Wrap the body at 72 characters**

In the body of your commit message, try to wrap lines at around 72 characters. This makes it easier to read, especially if someone is reviewing your code on a smaller screen or in a terminal.

**7: Use the body to explain what and why vs. how**

The subject line tells us what the commit does, but the body is where you get to explain why you did it. Don't get caught up in technical details or "how" you fixed the issue. Instead, focus on the "what" you did and, most importantly, "why" you did it. This is crucial for understanding the context of the change.


![that's a wrap](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/i855mgkidqxncp9eo8xj.gif)



---------

So there you have it, the seven golden rules of writing a fantastic Git commit message. Follow these guidelines, and your Git history will be clean, understandable, and a joy to work with. Plus, your fellow developers will thank you for it, and who knows, they might even invite you to their commit message appreciation party! 🎉

Happy coding, and may your Git history be evergreen! 🌱

_Until next time_


![cheers](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/jdix75qpi3bq35o268hl.jpeg)