Remove the feeds module

content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json

@@ -87,14 +87,5 @@
             "processed": "\n          <p>There are many good resources and interesting articles online about how to write good messages when committing changes to a Git repository.<\/p>\n\n<p>The post I often refer to is <a href=\"https:\/\/cbea.ms\/git-commit\">How to Write a Git Commit Message<\/a> by Chris Beams.<\/p>\n\n<p>In his post, he explains why good commit messages matter and gives these seven rules:<\/p>\n\n<blockquote>\n  <ul>\n  <li>Separate the subject from body with a blank line.<\/li>\n  <li>Limit the subject line to 50 characters.<\/li>\n  <li>Capitalize the subject line.<\/li>\n  <li>Do not end the subject line with a period.<\/li>\n  <li>Use the imperative mood in the subject line.<\/li>\n  <li>Wrap the body at 72 characters.<\/li>\n  <li>Use the body to explain what and why vs. how.<\/li>\n  <\/ul>\n<\/blockquote>\n\n<p>I'd recommend reading the article to get the full context.<\/p>\n\n<p>Rules two and six suggest lengths for the subject line and body which is another reason <a href=\"http:\/\/default\/daily\/2025\/04\/02\/commit\">why I rarely use <code>-m<\/code><\/a> when committing changes.<\/p>\n\n<p>Whilst you can create multi-line commit messages on the command line, by opening it in my preferred editor (Neovim for me), I can see where the lines should end and be warned if I exceed them.<\/p>\n\n<p>I can even include Chris' rules in my commit message template so I see them whenever I'm about to commit something.<\/p>\n\n<p>This additional feedback helps me create my commit messages how I intend.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "7430242f1d716198aa6fb01f727d1f9a",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }