7 Rules for Writing a Good Commit Messageby@pragativerma
2,111 reads
2,111 reads

7 Rules for Writing a Good Commit Message

by Pragati Verma4mJune 27th, 2022
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

Well-written commit messages that follow a standard format can help you and the viewers of your codebase to easily decipher the context of any specific change, the modules it affected, and why was it required. In this article, we’ll outline a widely accepted yet simple yet simple format for good commit messages, based on the Semantic Commits style popularized by the AngularJS team. The semantics of a good commit message are: The type of commit type, the scope of the commit, the body and the description.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - 7 Rules for Writing a Good Commit Message
Pragati Verma HackerNoon profile picture
Pragati Verma

Pragati Verma

@pragativerma

I am a Software Developer with a keen interest in tech content writing.

Learn More
LEARN MORE ABOUT @PRAGATIVERMA'S
EXPERTISE AND PLACE ON THE INTERNET.
L O A D I N G
. . . comments & more!

About Author

Pragati Verma HackerNoon profile picture
Pragati Verma@pragativerma
I am a Software Developer with a keen interest in tech content writing.

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite