Remove the feeds module

content/node.2a60b0b5-2ad5-42d2-8ed5-cf9f73e6f24b.json

@@ -87,14 +87,5 @@
             "processed": "\n          <p>Regardless of whether I was working as part of a team or individually, I used to create a new branch for every change. I'd do the work and merge the feature branch back into the mainline branch - usually either <code>main<\/code> or <code>develop<\/code>.<\/p>\n\n<p>When working on a team, conflicts are common that prevent different changes from being merged, and they're more likely the more time it's been since the last merge and how large the change is.<\/p>\n\n<p>Once, when demoing some in-progress work to a freelance client, I needed to switch branches as the changes were on different feature branches. Doing so broke my local environment and derailed the demo.<\/p>\n\n<h2 id=\"trunk-based-development\">Trunk-based development<\/h2>\n\n<p>These days, I advocate for and prefer to use trunk-based development. Instead of committing changes to feature branches, they are made directly to the mainline branch.<\/p>\n\n<p>As there are no feature branches, there are no merge conflicts when merging into mainline.<\/p>\n\n<p>Although there can still be conflicts when pulling remote changes, trunk-based development pairs nicely with continuous integration - when everyone works in small commits and pushes changes at least once daily. This makes conflicts less likely but also smaller and easier to resolve, and because everyone's changes are not hidden on feature branches, you know they will integrate and work together.<\/p>\n\n<p>It also stops me from breaking my environment during client demos!<\/p>\n\n        ",
             "summary": null
         }
-    ],
-    "feeds_item": [
-        {
-            "imported": "1970-01-01T00:32:50+00:00",
-            "guid": null,
-            "hash": "6b4f2625c11b6774d4cd0648c3870116",
-            "target_type": "feeds_feed",
-            "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
-        }
     ]
 }