42 lines
2.8 KiB
YAML
42 lines
2.8 KiB
YAML
uuid:
|
|
- value: 72aabaae-bf82-419b-a217-3b563126d9a9
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-06-03T20:44:43+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: "Good commit messages don't always matter"
|
|
created:
|
|
- value: '2025-06-01T20:16:10+00:00'
|
|
changed:
|
|
- value: '2025-06-03T20:44:43+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2025/06/01/good-commit-messages-dont-always-matter
|
|
langcode: en
|
|
body:
|
|
- value: "<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>"
|
|
format: full_html
|
|
processed: "<p>Writing <a href=\"http://default/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>"
|
|
summary: ''
|
|
field_daily_email_cta: { }
|