Thanks so much! I appreciate your kind words :)

Glad you like it, Yahaya! :)

Appreciate it, Ammaar! :)

Thanks a lot, Saanvi! :)

Hi Travis! I struggle too at times. This usually means I'm committing too much at once, and I split up the commit into two or more. Hope this was useful :)

Understood. Thanks Rafael B. Pires! I thought commits also have titles and bodies similar to pull requests 🤔

Prafful Javare

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 :)

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)

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!

:) Thank you, Antonin.

Thank you, Rafael! Glad you liked it :)

Thanks, Chijioke!