---
title: "Comment by Prafful Javare on \"Write Git Commit Messages That Your Colleagues Will Love\" | Hashnode"
description: "Loved these tips. I have been following the "imperative mood" styling ever since I read it in the contribution guide of a public repository. I usually"
url: "https://hashnode.com/posts/write-git-commit-messages-that-your-colleagues-will-love/62bef0301f580e1c22664421/comment/62c2129fc0401b3dcbcfb69f"
---

[Discussion](https://hashnode.com/posts/write-git-commit-messages-that-your-colleagues-will-love/62bef0301f580e1c22664421)

Comment [Write Git Commit Messages That Your Colleagues Will Love](https://hashnode.com/posts/write-git-commit-messages-that-your-colleagues-will-love/62bef0301f580e1c22664421)

[Prafful Javare](https://hashnode.com/@profgrammer)

[Jul 3, 2022](https://hashnode.com/posts/write-git-commit-messages-that-your-colleagues-will-love/62bef0301f580e1c22664421/comment/62c2129fc0401b3dcbcfb69f)

Loved these tips. I have been following the "imperative mood" styling ever since I read it in the contribution guide of a public repository. I usually use the vscode git extension for my commits, so can I separate the title from the body by adding a line break?

[Rafael B. Pires](https://hashnode.com/@bpires)

[Jul 3, 2022](https://hashnode.com/posts/write-git-commit-messages-that-your-colleagues-will-love/62bef0301f580e1c22664421/comment/62c2129fc0401b3dcbcfb69f#reply-62c21d49c0401b3dcbcfb762)

Hey Prafful, how are you? By VS Code extension do you mean the native source control tab? If so, I've learned recently that you can use enter to normally add multiple lines to the commit message before using ctrl+enter to submit. The first line would be considered the title and every line after would correspond to the description. In fact, Git per se doesn't differentiate title and description, these meanings are given by users/conventions.

[Prafful Javare](https://hashnode.com/@profgrammer)

[Jul 4, 2022](https://hashnode.com/posts/write-git-commit-messages-that-your-colleagues-will-love/62bef0301f580e1c22664421/comment/62c2129fc0401b3dcbcfb69f#reply-62c28180c0401b3dcbcfc1fd)

Understood. Thanks [Rafael B. Pires](https://hashnode.com/@bpires)! I thought commits also have titles and bodies similar to pull requests 🤔

[Simon Egersand 🎈](https://hashnode.com/@prplcode)

[Jul 4, 2022](https://hashnode.com/posts/write-git-commit-messages-that-your-colleagues-will-love/62bef0301f580e1c22664421/comment/62c2129fc0401b3dcbcfb69f#reply-62c2d1c5c0401b3dcbcfd3ff)

[Prafful Javare](https://hashnode.com/@profgrammer)

Hi. Yes, indeed Git does have a subject line ("title") as well as a body ("description"). I don't use VSCode so I don't know about that but when you use Git in the CLI you separate subject line and body with a newline. This is most likely what you need to do in VSCode as well :)

[Rafael B. Pires](https://hashnode.com/@bpires)

[Jul 9, 2022](https://hashnode.com/posts/write-git-commit-messages-that-your-colleagues-will-love/62bef0301f580e1c22664421/comment/62c2129fc0401b3dcbcfb69f#reply-62c9172ce62bf98e0fb073c4)

Simon, what I meant by Git doesn't differentiate title and description is that it's not required by default, but by good practices (which can include, also, the footer).

Here's what the docs say: "Though not required, it’s a good idea to begin the commit message with a single short (less than 50 characters) line summarizing the change, followed by a blank line and then a more thorough description. The text up to the first blank line in a commit message is treated as the commit title, and that title is used throughout Git." ([git-scm.com/docs/git-commit](https://git-scm.com/docs/git-commit#_discussion))

It's said that this soft rule was established from the analysis of the commits in the kernel codebase.

In fact, you can (and should) concatenate paragraphs, but you can also type just one very long commit message with all the descriptions, which is not recommended at all and would make the git log unreadable 😅

So, initially, the title and description are nothing more than just the first line, and the rest of the lines in the commit message, usually separated by a blank line, by convention. But, as you said, there's a subject line indeed 😌

I thought this could make it clearer for Prafful to visualize the usage in VS Code, but it made it more difficult instead. My bad, sorry!