Add daily emails
This commit is contained in:
parent
e642619988
commit
7b4efdf67f
5 changed files with 250 additions and 0 deletions
|
@ -6367,5 +6367,17 @@
|
|||
],
|
||||
"path_alias.e96bfd40-5093-47e3-8a2b-f006b88b22a4": [
|
||||
"node.01d84025-8b37-4456-b7f0-bf659c3f5a2b"
|
||||
],
|
||||
"node.72aabaae-bf82-419b-a217-3b563126d9a9": [
|
||||
"user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
||||
],
|
||||
"path_alias.dfd58cd1-37c0-4a26-af74-45ad7e212316": [
|
||||
"node.72aabaae-bf82-419b-a217-3b563126d9a9"
|
||||
],
|
||||
"node.121756bd-8e3e-4ba4-a0eb-76178deebc60": [
|
||||
"user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
||||
],
|
||||
"path_alias.ca472dde-6d81-4252-a780-22e5f3d0638f": [
|
||||
"node.121756bd-8e3e-4ba4-a0eb-76178deebc60"
|
||||
]
|
||||
}
|
92
content/node.121756bd-8e3e-4ba4-a0eb-76178deebc60.json
Normal file
92
content/node.121756bd-8e3e-4ba4-a0eb-76178deebc60.json
Normal file
|
@ -0,0 +1,92 @@
|
|||
{
|
||||
"uuid": [
|
||||
{
|
||||
"value": "121756bd-8e3e-4ba4-a0eb-76178deebc60"
|
||||
}
|
||||
],
|
||||
"langcode": [
|
||||
{
|
||||
"value": "en"
|
||||
}
|
||||
],
|
||||
"type": [
|
||||
{
|
||||
"target_id": "daily_email",
|
||||
"target_type": "node_type",
|
||||
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
||||
}
|
||||
],
|
||||
"revision_timestamp": [
|
||||
{
|
||||
"value": "2025-06-03T22:33:13+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": "Squashing commits can be OK"
|
||||
}
|
||||
],
|
||||
"created": [
|
||||
{
|
||||
"value": "2025-06-02T22:20:11+00:00"
|
||||
}
|
||||
],
|
||||
"changed": [
|
||||
{
|
||||
"value": "2025-06-03T22:33:13+00:00"
|
||||
}
|
||||
],
|
||||
"promote": [
|
||||
{
|
||||
"value": false
|
||||
}
|
||||
],
|
||||
"sticky": [
|
||||
{
|
||||
"value": false
|
||||
}
|
||||
],
|
||||
"default_langcode": [
|
||||
{
|
||||
"value": true
|
||||
}
|
||||
],
|
||||
"revision_translation_affected": [
|
||||
{
|
||||
"value": true
|
||||
}
|
||||
],
|
||||
"path": [
|
||||
{
|
||||
"alias": "",
|
||||
"pid": null,
|
||||
"langcode": "en"
|
||||
}
|
||||
],
|
||||
"body": [
|
||||
{
|
||||
"value": "<p>As well as <a href=\"\/daily\/2025\/04\/04\/good\">writing good commit messages<\/a>, I've previously written about <a href=\"\/daily\/2023\/01\/25\/to-squash-or-not-to-squash\">not squashing commits<\/a> when merging.<\/p><p>I think it's beneficial to keep the history of the commits that led to a change, especially if detailed messages have been written for some of the commits.<\/p><p>Typically, if the commits are squashed as part of a pull or merge request, the history and information is lost or all the messages are merged together - making them hard to read and, arguably, less valuable.<\/p><p>If you're working in a pair or mob and <a href=\"\/daily\/2025\/06\/01\/good-commit-messages-dont-always-matter\">creating temporary commits on a short-lived branch<\/a>, that's a situation when squashing commits is OK - as long as it's done properly.<\/p><p>I wouldn't have a generic automatically generated message.<\/p><p>I'd take the time to review the changes on the temporary branch and compare them to the mainline, remove any unrelated changes and write a new commit message that describes all the changes.<\/p><p>I'd make sure the new message is used and not lost when merged - especially when using online tools.<\/p><p>Then I can squash any temporary commits and merge the final squashed version.<\/p>",
|
||||
"format": "basic_html",
|
||||
"processed": "<p>As well as <a href=\"http:\/\/localhost:8888\/daily\/2025\/04\/04\/good\">writing good commit messages<\/a>, I've previously written about <a href=\"http:\/\/localhost:8888\/daily\/2023\/01\/25\/to-squash-or-not-to-squash\">not squashing commits<\/a> when merging.<\/p><p>I think it's beneficial to keep the history of the commits that led to a change, especially if detailed messages have been written for some of the commits.<\/p><p>Typically, if the commits are squashed as part of a pull or merge request, the history and information is lost or all the messages are merged together - making them hard to read and, arguably, less valuable.<\/p><p>If you're working in a pair or mob and <a href=\"http:\/\/localhost:8888\/daily\/2025\/06\/01\/good-commit-messages-dont-always-matter\">creating temporary commits on a short-lived branch<\/a>, that's a situation when squashing commits is OK - as long as it's done properly.<\/p><p>I wouldn't have a generic automatically generated message.<\/p><p>I'd take the time to review the changes on the temporary branch and compare them to the mainline, remove any unrelated changes and write a new commit message that describes all the changes.<\/p><p>I'd make sure the new message is used and not lost when merged - especially when using online tools.<\/p><p>Then I can squash any temporary commits and merge the final squashed version.<\/p>",
|
||||
"summary": ""
|
||||
}
|
||||
]
|
||||
}
|
92
content/node.72aabaae-bf82-419b-a217-3b563126d9a9.json
Normal file
92
content/node.72aabaae-bf82-419b-a217-3b563126d9a9.json
Normal file
|
@ -0,0 +1,92 @@
|
|||
{
|
||||
"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": "",
|
||||
"pid": null,
|
||||
"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:\/\/localhost:8888\/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": ""
|
||||
}
|
||||
]
|
||||
}
|
27
content/path_alias.ca472dde-6d81-4252-a780-22e5f3d0638f.json
Normal file
27
content/path_alias.ca472dde-6d81-4252-a780-22e5f3d0638f.json
Normal file
|
@ -0,0 +1,27 @@
|
|||
{
|
||||
"uuid": [
|
||||
{
|
||||
"value": "ca472dde-6d81-4252-a780-22e5f3d0638f"
|
||||
}
|
||||
],
|
||||
"langcode": [
|
||||
{
|
||||
"value": "en"
|
||||
}
|
||||
],
|
||||
"path": [
|
||||
{
|
||||
"value": "\/node\/121756bd-8e3e-4ba4-a0eb-76178deebc60"
|
||||
}
|
||||
],
|
||||
"alias": [
|
||||
{
|
||||
"value": "\/daily\/2025\/06\/02\/squashing-commits-can-be-ok"
|
||||
}
|
||||
],
|
||||
"status": [
|
||||
{
|
||||
"value": true
|
||||
}
|
||||
]
|
||||
}
|
27
content/path_alias.dfd58cd1-37c0-4a26-af74-45ad7e212316.json
Normal file
27
content/path_alias.dfd58cd1-37c0-4a26-af74-45ad7e212316.json
Normal file
|
@ -0,0 +1,27 @@
|
|||
{
|
||||
"uuid": [
|
||||
{
|
||||
"value": "dfd58cd1-37c0-4a26-af74-45ad7e212316"
|
||||
}
|
||||
],
|
||||
"langcode": [
|
||||
{
|
||||
"value": "en"
|
||||
}
|
||||
],
|
||||
"path": [
|
||||
{
|
||||
"value": "\/node\/72aabaae-bf82-419b-a217-3b563126d9a9"
|
||||
}
|
||||
],
|
||||
"alias": [
|
||||
{
|
||||
"value": "\/daily\/2025\/06\/01\/good-commit-messages-dont-always-matter"
|
||||
}
|
||||
],
|
||||
"status": [
|
||||
{
|
||||
"value": true
|
||||
}
|
||||
]
|
||||
}
|
Loading…
Add table
Add a link
Reference in a new issue