From c68b3485c7a49ad84d4ba83cbfc9b4ed85a37d51 Mon Sep 17 00:00:00 2001
From: Oliver Davies <oliver@oliverdavies.uk>
Date: Fri, 6 Jun 2025 23:07:21 +0100
Subject: [PATCH] Add daily email

---
 content/meta/index.json                       |  6 ++
 ....67695589-8db1-45fd-9940-3295330f55cc.json | 92 +++++++++++++++++++
 ....19207cf4-ec26-405c-84be-0153e68f17fb.json | 27 ++++++
 3 files changed, 125 insertions(+)
 create mode 100644 content/node.67695589-8db1-45fd-9940-3295330f55cc.json
 create mode 100644 content/path_alias.19207cf4-ec26-405c-84be-0153e68f17fb.json

diff --git a/content/meta/index.json b/content/meta/index.json
index 514c055a7..a4c93764d 100644
--- a/content/meta/index.json
+++ b/content/meta/index.json
@@ -6385,5 +6385,11 @@
     ],
     "path_alias.b33ea010-e6af-4237-8e49-07feb64c64b6": [
         "node.94a771d0-c280-408a-8ae7-c364cd573771"
+    ],
+    "node.67695589-8db1-45fd-9940-3295330f55cc": [
+        "user.b8966985-d4b2-42a7-a319-2e94ccfbb849"
+    ],
+    "path_alias.19207cf4-ec26-405c-84be-0153e68f17fb": [
+        "node.67695589-8db1-45fd-9940-3295330f55cc"
     ]
 }
\ No newline at end of file
diff --git a/content/node.67695589-8db1-45fd-9940-3295330f55cc.json b/content/node.67695589-8db1-45fd-9940-3295330f55cc.json
new file mode 100644
index 000000000..42fe94d95
--- /dev/null
+++ b/content/node.67695589-8db1-45fd-9940-3295330f55cc.json
@@ -0,0 +1,92 @@
+{
+    "uuid": [
+        {
+            "value": "67695589-8db1-45fd-9940-3295330f55cc"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "type": [
+        {
+            "target_id": "daily_email",
+            "target_type": "node_type",
+            "target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
+        }
+    ],
+    "revision_timestamp": [
+        {
+            "value": "2025-06-06T22:07:07+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": "Picking cherries"
+        }
+    ],
+    "created": [
+        {
+            "value": "2025-06-04T22:04:43+00:00"
+        }
+    ],
+    "changed": [
+        {
+            "value": "2025-06-06T22:07:07+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>If you're working on a feature branch, or a <a href=\"\/daily\/2025\/06\/01\/good-commit-messages-dont-always-matter\">temporary branch for pair or mob programming<\/a>, what do you do if you accidentally commit a change to the wrong branch?<\/p><p>Do you reset your changes, switch to the correct branch and re-create the same changes manually?<\/p><p>You don't need to.<\/p><p>Git has a solution for this.<\/p><p>Create the commit as you would on the correct branch and copy the commit SHA.<\/p><p>Use <code>git checkout<\/code> or <code>git switch<\/code> to move to the correct branch and use <code>git cherry-pick<\/code> with the commit SHA.<\/p><p>It will pluck the commit from the branch and re-apply the changes with the same commit message.<\/p><p>Then, if you merge or rebase your temporary branch, Git will know the change has already been applied and skip that commit.<\/p><p>No need to re-do the same changes again manually.<\/p>",
+            "format": "basic_html",
+            "processed": "<p>If you're working on a feature branch, or a <a href=\"http:\/\/localhost:8888\/daily\/2025\/06\/01\/good-commit-messages-dont-always-matter\">temporary branch for pair or mob programming<\/a>, what do you do if you accidentally commit a change to the wrong branch?<\/p><p>Do you reset your changes, switch to the correct branch and re-create the same changes manually?<\/p><p>You don't need to.<\/p><p>Git has a solution for this.<\/p><p>Create the commit as you would on the correct branch and copy the commit SHA.<\/p><p>Use <code>git checkout<\/code> or <code>git switch<\/code> to move to the correct branch and use <code>git cherry-pick<\/code> with the commit SHA.<\/p><p>It will pluck the commit from the branch and re-apply the changes with the same commit message.<\/p><p>Then, if you merge or rebase your temporary branch, Git will know the change has already been applied and skip that commit.<\/p><p>No need to re-do the same changes again manually.<\/p>",
+            "summary": ""
+        }
+    ]
+}
\ No newline at end of file
diff --git a/content/path_alias.19207cf4-ec26-405c-84be-0153e68f17fb.json b/content/path_alias.19207cf4-ec26-405c-84be-0153e68f17fb.json
new file mode 100644
index 000000000..3277c406d
--- /dev/null
+++ b/content/path_alias.19207cf4-ec26-405c-84be-0153e68f17fb.json
@@ -0,0 +1,27 @@
+{
+    "uuid": [
+        {
+            "value": "19207cf4-ec26-405c-84be-0153e68f17fb"
+        }
+    ],
+    "langcode": [
+        {
+            "value": "en"
+        }
+    ],
+    "path": [
+        {
+            "value": "\/node\/67695589-8db1-45fd-9940-3295330f55cc"
+        }
+    ],
+    "alias": [
+        {
+            "value": "\/daily\/2025\/06\/04\/picking-cherries"
+        }
+    ],
+    "status": [
+        {
+            "value": true
+        }
+    ]
+}
\ No newline at end of file