68 lines
2.9 KiB
YAML
68 lines
2.9 KiB
YAML
uuid:
|
|
- value: 74b360bb-61b3-4ed4-8942-1c21bdf630ef
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:14+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: "Don't delete my commit messages"
|
|
created:
|
|
- value: '2024-05-11T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:14+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/05/11/don-t-delete-my-commit-messages
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>Another reason I don't like squashing commits within pull/merge request is losing detail within the commit messages.</p>
|
|
|
|
<p>As someone who usually writes detailed commit messages that explain why the change is being made, any gotchas or alternative approaches that were tried, etc, I want that information to be retained.</p>
|
|
|
|
<p>Previously, when working on a team and doing merge/pull requests, when merging a feature or release branch, either the tool or reviewer would delete all the messages from the squashed commits.</p>
|
|
|
|
<p>The time I spent writing the messages was wasted, and the information was lost.</p>
|
|
|
|
<p>I'd rather <a href="/daily/2024/05/10/optimise-for-revertability">keep the original commits intact</a> but, if you need to squash commits, please don't remove the previous messages as they could be useful in the future.</p>
|
|
|
|
<p>People can see the changes by viewing the commits, but the information within the commit messages are valuable, too.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>Another reason I don't like squashing commits within pull/merge request is losing detail within the commit messages.</p>
|
|
|
|
<p>As someone who usually writes detailed commit messages that explain why the change is being made, any gotchas or alternative approaches that were tried, etc, I want that information to be retained.</p>
|
|
|
|
<p>Previously, when working on a team and doing merge/pull requests, when merging a feature or release branch, either the tool or reviewer would delete all the messages from the squashed commits.</p>
|
|
|
|
<p>The time I spent writing the messages was wasted, and the information was lost.</p>
|
|
|
|
<p>I'd rather <a href="http://default/daily/2024/05/10/optimise-for-revertability">keep the original commits intact</a> but, if you need to squash commits, please don't remove the previous messages as they could be useful in the future.</p>
|
|
|
|
<p>People can see the changes by viewing the commits, but the information within the commit messages are valuable, too.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|