{ "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
Following last week's email on different ways to write .gitignore files<\/a>, friend of the list, Daniel Harper, sent me this reply (shared with permission):<\/p>\n\n 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 This is a good point.<\/p>\n\n What do people expect to see in a A list of directories and files to be ignored or allowed?<\/p>\n\n Based on the filename, it should be the former.<\/p>\n\n This would be clearer for people when they first open the file.<\/p>\n\n However, if you decide to use the allow approach instead, document it in an 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 Following last week's email on different ways to write .gitignore files<\/a>, friend of the list, Daniel Harper, sent me this reply (shared with permission):<\/p>\n\n 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 This is a good point.<\/p>\n\n What do people expect to see in a A list of directories and files to be ignored or allowed?<\/p>\n\n Based on the filename, it should be the former.<\/p>\n\n This would be clearer for people when they first open the file.<\/p>\n\n However, if you decide to use the allow approach instead, document it in an 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
}
],
"feeds_item": [
{
"imported": "2025-05-11T09:00:20+00:00",
"guid": null,
"hash": "8c32951c32d678ca2fe6bac26a108dcb",
"target_type": "feeds_feed",
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
}
]
}\n
.gitignore<\/code> file?<\/p>\n\n
\n
.gitignore<\/code> file?<\/p>\n\n