80 lines
3 KiB
YAML
80 lines
3 KiB
YAML
uuid:
|
|
- value: a2dbc5b2-ae56-4583-bc9f-ec0f70601eae
|
|
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 or .gitallow'
|
|
created:
|
|
- value: '2024-02-05T00: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/02/05/gitignore-or-gitallow
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>Following last week's email on <a href="/daily/2024/01/27/gitignore-inclusive-or-exclusive">different ways to write .gitignore files</a>, friend of the list, Daniel Harper, sent me this reply (shared with permission):</p>
|
|
|
|
<blockquote>
|
|
<p>I had a debate once about this topic and we settled on ignore as the filename explicitly describes what it should be doing ie. It's not .gitallow 😆</p>
|
|
</blockquote>
|
|
|
|
<p>This is a good point.</p>
|
|
|
|
<p>What do people expect to see in a <code>.gitignore</code> file?</p>
|
|
|
|
<p>A list of directories and files to be ignored or allowed?</p>
|
|
|
|
<p>Based on the filename, it should be the former.</p>
|
|
|
|
<p>This would be clearer for people when they first open the file.</p>
|
|
|
|
<p>However, if you decide to use the allow approach instead, document it in an <a href="/daily/2022/09/23/adrs-technical-design-documents">ADR or design document</a> and why you decided to do it that way and provide context for people working on the codebase in the future.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>Following last week's email on <a href="/daily/2024/01/27/gitignore-inclusive-or-exclusive">different ways to write .gitignore files</a>, friend of the list, Daniel Harper, sent me this reply (shared with permission):</p>
|
|
|
|
<blockquote>
|
|
<p>I had a debate once about this topic and we settled on ignore as the filename explicitly describes what it should be doing ie. It's not .gitallow 😆</p>
|
|
</blockquote>
|
|
|
|
<p>This is a good point.</p>
|
|
|
|
<p>What do people expect to see in a <code>.gitignore</code> file?</p>
|
|
|
|
<p>A list of directories and files to be ignored or allowed?</p>
|
|
|
|
<p>Based on the filename, it should be the former.</p>
|
|
|
|
<p>This would be clearer for people when they first open the file.</p>
|
|
|
|
<p>However, if you decide to use the allow approach instead, document it in an <a href="/daily/2022/09/23/adrs-technical-design-documents">ADR or design document</a> and why you decided to do it that way and provide context for people working on the codebase in the future.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|