100 lines
No EOL
3.6 KiB
JSON
100 lines
No EOL
3.6 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "625396bb-20aa-4f43-9b8f-f297b593d89f"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-21T01:22:00+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": "Debugging gitignore rules\n"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2022-12-28T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-21T01:22:00+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2022\/12\/28\/debugging-gitignore-rules",
|
|
"langcode": null
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Have you wondered why a file or directory is being ignored in your Git repository and isn't appearing when you run <code>git status<\/code>?<\/p>\n\n<p>Maybe you have multiple <code>.gitignore<\/code> files and you don't know which is causing the issue, or you ignore everything and explicitly unignore the files that you want to add.<\/p>\n\n<h2 id=\"%60check-ignore%60-to-the-rescue\"><code>check-ignore<\/code> to the rescue<\/h2>\n\n<p><code>git check-ignore<\/code> accepts a list of paths and checks if each is ignored.<\/p>\n\n<p>There's also a <code>--verbose<\/code> option that will tell you which <code>.gitignore<\/code> file is causing it to be ignored as well as the line number and the pattern - great information for debugging, and no more force adding files.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Have you wondered why a file or directory is being ignored in your Git repository and isn't appearing when you run <code>git status<\/code>?<\/p>\n\n<p>Maybe you have multiple <code>.gitignore<\/code> files and you don't know which is causing the issue, or you ignore everything and explicitly unignore the files that you want to add.<\/p>\n\n<h2 id=\"%60check-ignore%60-to-the-rescue\"><code>check-ignore<\/code> to the rescue<\/h2>\n\n<p><code>git check-ignore<\/code> accepts a list of paths and checks if each is ignored.<\/p>\n\n<p>There's also a <code>--verbose<\/code> option that will tell you which <code>.gitignore<\/code> file is causing it to be ignored as well as the line number and the pattern - great information for debugging, and no more force adding files.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-21T01:22:00+00:00",
|
|
"guid": null,
|
|
"hash": "b132c7f6277c6bbb308c6905d1673959",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |