Commit Naming Rules

follow
covered by dxscanner.io
2 Contributors contributor avatar contributor avatar
4 minutes read
Last updated 03 May 10:41

TL;DR

Having a commit naming convention can be of great help, in maintaining the codebase and easing up the development process. Find out more about the good practices around commit naming rules!

Commit naming guide
Source: Author unknown

Why You Might Want Commit Naming Rules?

Commit messages have become a crucial part of the development process. They allow you to trace back the point in time when you wrote that particular piece of code, or more often they let other developers in your team, track the flow of code, and no one likes tracking code with messy commit messages. Since it is a summary of what changes you did, it is very important to write commit messages that are concise and consistent.

There are many conventions around commit messages, that are widely followed in the developer community.

Problems that Commit Naming Rules Helps to Solve

How to Implement Commit Naming Rules?

Commit Message

Add a Type

Commit messages should indicate the type of commit. For that following type you should use these conventions:

  • fix: Indicates that your commit fixes some bug or something.
  • feat: Indicates that your commit adds a new feature.

Besides these many organizations like Angular, use their conventions and commit types like 'build:', 'docs:', 'refactor:', etc.

Write Commit Message In the Imperative Mood

Commit messages, especially you should write the subject lines in the imperative mood, i.e., as if you were to command your code to perform some instruction. Like telling what Git should do while applying that commit.

eg. instead of using "fixed: bug #45", use "fix: bug #45" .

Explain the What's and Why's Instead of How

The commit message body is the perfect place to explain what your commit does. Don't explain how you did the changes. Instead, show what and why you changed. Commit body is the perfect place to explain these things. Generally, your code should be self-explanatory. Still, if you feel the need to explain how something works, use source comments.

Commit Convetions

If your repo has unusual commit tags, create a commit conventions document for your team. Commit Conventions are especially helpful when you maintain an open-source repo since they provide guidelines for every contributor. However, if you are using the standard fix, feat, bug, refactoring, and so on, you don't need to have them written down.

Besides all these commit naming conventions, there are things that are highly subjective and may vary between developers to developers, like "should the subject line be capitalized?" or "to add or not to add punctuation marks in commit messages?". Opinions like these may vary from person to person but it's a good practice to be consistent with your conventions.

Common Pitfalls of Commit Naming Rules

Free consultation

Free consultation

Prokop Simek
Ask for free