100 lines
No EOL
3.7 KiB
JSON
100 lines
No EOL
3.7 KiB
JSON
{
|
|
"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": "\n <p>Add everything and ignore what you don't want, or ignore everything and explicitly add what you need.<\/p>\n\n<p>There are two ways to structure a .gitignore file.<\/p>\n\n<p>The default approach is that all files can be added, and you specify the files and directories you want to ignore.<\/p>\n\n<p>For example, if my <code>.gitignore<\/code> file was this, these two directories would be ignored:<\/p>\n\n<pre><code class=\"language-plain\">vendor\nweb\n<\/code><\/pre>\n\n<p>The other approach is to ignore everything and unignore the things to add. For example:<\/p>\n\n<pre><code class=\"language-plain\">*\n!build.yaml\n!Dockerfile\n!docker-compose.yaml\n!web\/*\/custom\n<\/code><\/pre>\n\n<p>Both approaches work and are regularly used.<\/p>\n\n<p>Which approach do you prefer and why?<\/p>\n\n<p>Reply and let me know.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Add everything and ignore what you don't want, or ignore everything and explicitly add what you need.<\/p>\n\n<p>There are two ways to structure a .gitignore file.<\/p>\n\n<p>The default approach is that all files can be added, and you specify the files and directories you want to ignore.<\/p>\n\n<p>For example, if my <code>.gitignore<\/code> file was this, these two directories would be ignored:<\/p>\n\n<pre><code class=\"language-plain\">vendor\nweb\n<\/code><\/pre>\n\n<p>The other approach is to ignore everything and unignore the things to add. For example:<\/p>\n\n<pre><code class=\"language-plain\">*\n!build.yaml\n!Dockerfile\n!docker-compose.yaml\n!web\/*\/custom\n<\/code><\/pre>\n\n<p>Both approaches work and are regularly used.<\/p>\n\n<p>Which approach do you prefer and why?<\/p>\n\n<p>Reply and let me know.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "1970-01-01T00:33:45+00:00",
|
|
"guid": null,
|
|
"hash": "5b63bfce940fe7e208810bb77d3cd2d6",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |