Remove the feeds module

content/node.235bcd7b-1bdb-4616-99bb-ecd321f449a0.json

@@ -87,14 +87,5 @@
             "processed": "\n          <p>I was recently asked about setting up different testing environments based on topic (a.k.a. feature) branches.<\/p>\n\n<p>When a feature or bug fix was finished, it would create a new environment for it to be tested.<\/p>\n\n<p>If it passed testing, the topic branch was merged and it would be included in the next release.<\/p>\n\n<p>But, there's no guarantee it still works once it's been merged.<\/p>\n\n<p>It could conflict with changes from a different topic branch and no longer work - even if it worked when it was tested in isolation on its own branch.<\/p>\n\n<p>To ensure it still works, it will need to be tested again.<\/p>\n\n<p>So, what is the benefit of testing it in isolation if it needs to be tested again once it's merged?<\/p>\n\n<p>This is why I prefer continuous integration and delivery (CI\/CD), as I always know all changes work together and not just in isolation.<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "a3e94e918c387456f8b5d5871cf5e306",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }