Migrate content to YAML
This commit is contained in:
parent
3d76aa0c3b
commit
9d5a930eab
4550 changed files with 93849 additions and 129734 deletions
98
content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.yml
Normal file
98
content/node.2f257fd0-6e5d-4690-9f01-3435e3578798.yml
Normal file
|
@ -0,0 +1,98 @@
|
|||
uuid:
|
||||
- value: 2f257fd0-6e5d-4690-9f01-3435e3578798
|
||||
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:20+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: 'gitignore - inclusive or exclusive?'
|
||||
created:
|
||||
- value: '2024-01-27T00:00:00+00:00'
|
||||
changed:
|
||||
- value: '2025-05-11T09:00:20+00:00'
|
||||
promote:
|
||||
- value: false
|
||||
sticky:
|
||||
- value: false
|
||||
default_langcode:
|
||||
- value: true
|
||||
revision_translation_affected:
|
||||
- value: true
|
||||
path:
|
||||
- alias: /daily/2024/01/27/gitignore-inclusive-or-exclusive
|
||||
langcode: en
|
||||
body:
|
||||
- value: |
|
||||
<p>Add everything and ignore what you don't want, or ignore everything and explicitly add what you need.</p>
|
||||
|
||||
<p>There are two ways to structure a .gitignore file.</p>
|
||||
|
||||
<p>The default approach is that all files can be added, and you specify the files and directories you want to ignore.</p>
|
||||
|
||||
<p>For example, if my <code>.gitignore</code> file was this, these two directories would be ignored:</p>
|
||||
|
||||
<pre><code class="language-plain">vendor
|
||||
web
|
||||
</code></pre>
|
||||
|
||||
<p>The other approach is to ignore everything and unignore the things to add. For example:</p>
|
||||
|
||||
<pre><code class="language-plain">*
|
||||
!build.yaml
|
||||
!Dockerfile
|
||||
!docker-compose.yaml
|
||||
!web/*/custom
|
||||
</code></pre>
|
||||
|
||||
<p>Both approaches work and are regularly used.</p>
|
||||
|
||||
<p>Which approach do you prefer and why?</p>
|
||||
|
||||
<p>Reply and let me know.</p>
|
||||
|
||||
|
||||
format: full_html
|
||||
processed: |
|
||||
<p>Add everything and ignore what you don't want, or ignore everything and explicitly add what you need.</p>
|
||||
|
||||
<p>There are two ways to structure a .gitignore file.</p>
|
||||
|
||||
<p>The default approach is that all files can be added, and you specify the files and directories you want to ignore.</p>
|
||||
|
||||
<p>For example, if my <code>.gitignore</code> file was this, these two directories would be ignored:</p>
|
||||
|
||||
<pre><code class="language-plain">vendor
|
||||
web
|
||||
</code></pre>
|
||||
|
||||
<p>The other approach is to ignore everything and unignore the things to add. For example:</p>
|
||||
|
||||
<pre><code class="language-plain">*
|
||||
!build.yaml
|
||||
!Dockerfile
|
||||
!docker-compose.yaml
|
||||
!web/*/custom
|
||||
</code></pre>
|
||||
|
||||
<p>Both approaches work and are regularly used.</p>
|
||||
|
||||
<p>Which approach do you prefer and why?</p>
|
||||
|
||||
<p>Reply and let me know.</p>
|
||||
|
||||
|
||||
summary: null
|
||||
field_daily_email_cta: { }
|
Loading…
Add table
Add a link
Reference in a new issue