Move all files to tome/

tome/content/node.7d242a44-c31b-419e-848e-73eba79f962e.yml

@@ -0,0 +1,83 @@
+uuid:
+  - value: 7d242a44-c31b-419e-848e-73eba79f962e
+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:38+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: |
+      Are you really doing CI/CD?
+created:
+  - value: '2023-06-18T00:00:00+00:00'
+changed:
+  - value: '2025-05-11T09:00:38+00:00'
+promote:
+  - value: false
+sticky:
+  - value: false
+default_langcode:
+  - value: true
+revision_translation_affected:
+  - value: true
+path:
+  - alias: /daily/2023/06/18/are-you-doing-ci-cd
+    langcode: en
+body:
+  - value: |
+      <p>Does your team really do CI/CD (continuous integration and delivery)?</p>
+
+      <p>I recently watched a recording of a talk from another daily emailer, <a href="https://jhall.io">Jonathan Hall</a>, who started by asking the audience to raise their hands and keep them raised if...</p>
+
+      <ul>
+      <li>They did a release to production in the last week.</li>
+      <li>They did a release to production yesterday.</li>
+      <li>They do not have a permanent branch called <code>develop</code>.</li>
+      <li>They do not have a special "hotfix" procedure.</li>
+      <li>Every Developer on their team merged work into <code>main</code> yesterday.</li>
+      <li>They have no pull requests more than 24 hours old.</li>
+      </ul>
+
+      <h2 id="ci%2Fcd-is-about-process">CI/CD is about process</h2>
+
+      <p>This is an excellent way to highlight that CI/CD is about processes, not technologies.</p>
+
+      <p>Continuous integration is about how often everyone merges and pushes their changes, and continuous delivery and deployment is how you create releasable software and how long it takes for a change to get into production - not whether or not you use GitHub Actions, GitLab CI, CircleCI or Jenkins.</p>
+
+              
+    format: full_html
+    processed: |
+      <p>Does your team really do CI/CD (continuous integration and delivery)?</p>
+
+      <p>I recently watched a recording of a talk from another daily emailer, <a href="https://jhall.io">Jonathan Hall</a>, who started by asking the audience to raise their hands and keep them raised if...</p>
+
+      <ul>
+      <li>They did a release to production in the last week.</li>
+      <li>They did a release to production yesterday.</li>
+      <li>They do not have a permanent branch called <code>develop</code>.</li>
+      <li>They do not have a special "hotfix" procedure.</li>
+      <li>Every Developer on their team merged work into <code>main</code> yesterday.</li>
+      <li>They have no pull requests more than 24 hours old.</li>
+      </ul>
+
+      <h2 id="ci%2Fcd-is-about-process">CI/CD is about process</h2>
+
+      <p>This is an excellent way to highlight that CI/CD is about processes, not technologies.</p>
+
+      <p>Continuous integration is about how often everyone merges and pushes their changes, and continuous delivery and deployment is how you create releasable software and how long it takes for a change to get into production - not whether or not you use GitHub Actions, GitLab CI, CircleCI or Jenkins.</p>
+
+              
+    summary: null
+field_daily_email_cta: {  }