Move all files to tome/
This commit is contained in:
parent
5675bcfc36
commit
674daab35b
2874 changed files with 0 additions and 0 deletions
65
tome/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.yml
Normal file
65
tome/content/node.2eadbc08-32b4-4485-9cfd-087223e7040b.yml
Normal file
|
@ -0,0 +1,65 @@
|
|||
uuid:
|
||||
- value: 2eadbc08-32b4-4485-9cfd-087223e7040b
|
||||
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: |
|
||||
A CI pipeline is like an additional team member
|
||||
created:
|
||||
- value: '2023-06-27T00: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/27/ci-pipeline-additional-team-member
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>Imagine having a team member who tests each feature before every deployment, reviews the code to ensure its style is consistent, runs quality checks like linting and static analysis, and checks for insecure dependencies.</p>
|
||||
|
||||
<p>If those checks all pass, they automatically deploy the changes and make them live or update a pre-production environment.</p>
|
||||
|
||||
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
||||
|
||||
<p>A CI pipeline can do that. Automatically. For every commit and change to your codebase.</p>
|
||||
|
||||
<p>Having a CI pipeline is like having an additional team member and one who's always ready and waiting for someone to push a change to test.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>Imagine having a team member who tests each feature before every deployment, reviews the code to ensure its style is consistent, runs quality checks like linting and static analysis, and checks for insecure dependencies.</p>
|
||||
|
||||
<p>If those checks all pass, they automatically deploy the changes and make them live or update a pre-production environment.</p>
|
||||
|
||||
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
||||
|
||||
<p>A CI pipeline can do that. Automatically. For every commit and change to your codebase.</p>
|
||||
|
||||
<p>Having a CI pipeline is like having an additional team member and one who's always ready and waiting for someone to push a change to test.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue