When you code, do you already know what goes into your commit messages when creating pull requests? 🤔
It’s not a topic we often discuss, but I’ve found that being intentional with commit messages naturally shapes how I organize my pull requests.
In fact, thinking about how you’ll structure your commits before you even begin coding can significantly benefit your development process in two major ways:
It naturally helps you structure your work: Thinking about the commit message beforehand naturally informs what goes into each commit. For example, you’ll start to distinguish between commits that add new files and those that improve existing features. This makes your commits more logical and easier to track.
It improves code clarity for others and yourself: A clear commit message helps the reviewer understand the purpose of each change. It also aids you in the future when revisiting your code—whether for bug fixes or adding new features—since you'll be able to easily identify what was done in each commit.
Practical Benefits of “Conventional Commits”
To keep things consistent, I’ve been using the “Conventional Commits” standard.
If you’re unfamiliar, Conventional Commits is a standardized way to write commit messages using the format:
type(scope): description.
This format isn’t just about aesthetics—it makes commits more human-readable and machine-processable, which opens the door to automation. For example, tools can use these messages to generate changelogs, handle versioning, or even enforce commit rules in CI/CD pipelines.
By using prefixes like feat, fix, or docs, you quickly convey the intent of each change, improving both collaboration and traceability.
Here’s a quick example of a “Conventional Commit”:
feat: implement filters for product search by price and category
You can tell it’s simple, clear, and instantly communicates the purpose of the change.
Make It Easier with VS Code
One great thing about “Conventional Commits” is that you don’t have to memorize the format. If you use VS Code, there’s an extension to simplify the process:
👉 Install the Conventional Commits Extension
This extension guides you through creating standardized commit messages right from your editor, making it easier to adopt this practice. It's so easy.
Wrapping Up
Being intentional about commit messages might seem like extra work at first, but it’s an investment that pays off VERY QUICKLY. With “Conventional Commits,” you’ll find your workflow becoming more structured, your pull requests clearer, and your development experience smoother overall.
Top comments (0)