8 lines
1.1 KiB
Markdown
8 lines
1.1 KiB
Markdown
|
---
|
||
|
|
date: 2025-06-01
|
||
|
|
title: Good commit messages don't always matter
|
||
|
|
permalink: /daily/2025/06/01/good-commit-messages-dont-always-matter
|
||
|
|
---
|
||
|
|
|
||
|
|
<p>Writing <a href=\"/daily/2024/05/17/why-i-dont-commit-with--m\">good commit messages</a> is important.</p><p>A good commit message doesn't just describe what changed, it captures why it was changed.</p><p>It can detail other approaches that were considered or tried before deciding on the end solution.</p><p>It can contain links to relevant issues, documentation pages, blog posts or videos.</p><p>It can document any manual deployment steps, or follow-up actions that will be addressed in future commits.</p><p>This all makes sense for permanent commits.</p><p>But, sometimes you may make a temporary commit that won't always remain in the codebase.</p><p>For example, if you're working in a pair or mob programming session, you want to be able to switch drivers as quickly and seamlessly as possible.</p><p>In that situation, you just need a basic commit message to share the latest changes, so a quick <code>wip</code> commit is fine and it can be amended later.</p>
|