<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RepositoryStructure on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/repositorystructure/</link><description>Recent content in RepositoryStructure on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 05 Sep 2024 18:48:29 +0200</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/repositorystructure/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Organize Code Across Git Repositories</title><link>http://blog.marko-apfel.de/posts/repository-organization/</link><pubDate>Fri, 30 Aug 2024 09:40:05 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/repository-organization/</guid><description>A short set of rules for deciding what gets its own repository, how to name it, and how to keep experimental code from cluttering your core product.</description></item><item><title>Production Code vs. Non-Production Code: Why the Distinction Matters</title><link>http://blog.marko-apfel.de/posts/production-vs-non-production-code/</link><pubDate>Fri, 30 Aug 2024 09:40:05 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/production-vs-non-production-code/</guid><description>Where do integration tests belong relative to your source tree? The answer says more about your repository&amp;rsquo;s structure than it first appears.</description></item></channel></rss>