Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
76
content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.yml
Normal file
76
content/node.c1064abb-f7f8-4e4d-bfb7-9842271b0938.yml
Normal file
|
@ -0,0 +1,76 @@
|
|||
uuid:
|
||||
- value: c1064abb-f7f8-4e4d-bfb7-9842271b0938
|
||||
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:00+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: 'Feature branching slows delivery'
|
||||
created:
|
||||
- value: '2025-03-05T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:00+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2025/03/05/slow
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>As well as <a href="/daily/2025/02/18/conflicts">causing merge conflicts</a>, feature branches slow the delivery of new features.</p>
|
||||
|
||||
<p>Someone needs to be responsible for merging the branches once they've been reviewed and approved, and any further merges into release branches.</p>
|
||||
|
||||
<p>This is typically the Lead Developer on the project, but this person then becomes a bottleneck.</p>
|
||||
|
||||
<p>They need to oversee all the branches and merges, and know what needs to be merged and where it needs to be deployed.</p>
|
||||
|
||||
<p>This slows down the speed of delivery.</p>
|
||||
|
||||
<p>In a trunk-based environment, there's only one branch and everyone can commit and push to it.</p>
|
||||
|
||||
<p>And, if you're <a href="/daily/2025/02/17/ci-cd">doing continuous delivery</a>, any changes will be automatically deployed.</p>
|
||||
|
||||
<p>No more bottleneck.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>As well as <a href="http://default/daily/2025/02/18/conflicts">causing merge conflicts</a>, feature branches slow the delivery of new features.</p>
|
||||
|
||||
<p>Someone needs to be responsible for merging the branches once they've been reviewed and approved, and any further merges into release branches.</p>
|
||||
|
||||
<p>This is typically the Lead Developer on the project, but this person then becomes a bottleneck.</p>
|
||||
|
||||
<p>They need to oversee all the branches and merges, and know what needs to be merged and where it needs to be deployed.</p>
|
||||
|
||||
<p>This slows down the speed of delivery.</p>
|
||||
|
||||
<p>In a trunk-based environment, there's only one branch and everyone can commit and push to it.</p>
|
||||
|
||||
<p>And, if you're <a href="http://default/daily/2025/02/17/ci-cd">doing continuous delivery</a>, any changes will be automatically deployed.</p>
|
||||
|
||||
<p>No more bottleneck.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue