oliverdavies.uk/content/node.a2dbc5b2-ae56-4583-bc9f-ec0f70601eae.json

{
    "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": "\n          <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>\n\n<blockquote>\n  <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 \ud83d\ude06<\/p>\n<\/blockquote>\n\n<p>This is a good point.<\/p>\n\n<p>What do people expect to see in a <code>.gitignore<\/code> file?<\/p>\n\n<p>A list of directories and files to be ignored or allowed?<\/p>\n\n<p>Based on the filename, it should be the former.<\/p>\n\n<p>This would be clearer for people when they first open the file.<\/p>\n\n<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>\n\n        ",
            "format": "full_html",
            "processed": "\n          <p>Following last week's email on <a href=\"http:\/\/default\/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>\n\n<blockquote>\n  <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 \ud83d\ude06<\/p>\n<\/blockquote>\n\n<p>This is a good point.<\/p>\n\n<p>What do people expect to see in a <code>.gitignore<\/code> file?<\/p>\n\n<p>A list of directories and files to be ignored or allowed?<\/p>\n\n<p>Based on the filename, it should be the former.<\/p>\n\n<p>This would be clearer for people when they first open the file.<\/p>\n\n<p>However, if you decide to use the allow approach instead, document it in an <a href=\"http:\/\/default\/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>\n\n        ",
            "summary": null
        }
    ]
}