Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
64
content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.yml
Normal file
64
content/node.d33493db-20b9-4946-94a1-bc2abfb6b998.yml
Normal file
|
@ -0,0 +1,64 @@
|
|||
uuid:
|
||||
- value: d33493db-20b9-4946-94a1-bc2abfb6b998
|
||||
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:05+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: 'git stash is underrated'
|
||||
created:
|
||||
- value: '2024-10-24T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:05+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2024/10/24/git-stash-is-underrated
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p><code>git stash</code> is one of the commands I use the most.</p>
|
||||
|
||||
<p>Maybe because I do trunk-based development so I very rarely create new branches, or because I intentionally make and push small atomic commits, I often find myself using <code>git stash</code> whilst debugging something or if I need to switch contexts quickly whilst in the middle of another task and I don't want to lose my changes.</p>
|
||||
|
||||
<p>If it's not something I'm going to unstash and bring back almost immediately, I can create a new branch or create a named stash with <code>git stash save <name></code>.</p>
|
||||
|
||||
<p>If I don't need to stash everything, it supports the <code>-p</code> or <code>--patch</code> option and I can decide what to stash and what to keep.</p>
|
||||
|
||||
<p>If you haven't used <code>git stash</code>, I recommend giving it a try.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p><code>git stash</code> is one of the commands I use the most.</p>
|
||||
|
||||
<p>Maybe because I do trunk-based development so I very rarely create new branches, or because I intentionally make and push small atomic commits, I often find myself using <code>git stash</code> whilst debugging something or if I need to switch contexts quickly whilst in the middle of another task and I don't want to lose my changes.</p>
|
||||
|
||||
<p>If it's not something I'm going to unstash and bring back almost immediately, I can create a new branch or create a named stash with <code>git stash save <name></code>.</p>
|
||||
|
||||
<p>If I don't need to stash everything, it supports the <code>-p</code> or <code>--patch</code> option and I can decide what to stash and what to keep.</p>
|
||||
|
||||
<p>If you haven't used <code>git stash</code>, I recommend giving it a try.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue