---
title: "#multi-repo articles | Hashnode"
description: "Explore 2 articles tagged #multi-repo on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/multi-repo"
---

Tag

# #multi-repo

2 posts · 0 followers

[akshay Nikhare](https://hashnode.com/@akshaynikhare) · [Jul 24](https://hashnode.com/posts/mono-repo-multi-repo-how-we-structured-6-apps-across-4-repositories/6a639f9dd77128849a5c929f)

### [Mono-Repo + Multi-Repo: How We Structured 6 Apps Across 4 Repositories](https://akshaynikhare.hashnode.dev/mono-repo-multi-repo-how-we-structured-6-apps-across-4-repositories?utm_source=hashnode&utm_medium=feed)

Most teams treat "monorepo vs multi-repo" as a binary choice. Pick one, commit, move on. We ended up with a hybrid, and it turned out to be the right call — not out of indecision, but because our apps

6 min read · [akshaynikhare.hashnode.dev](https://akshaynikhare.hashnode.dev/mono-repo-multi-repo-how-we-structured-6-apps-across-4-repositories?utm_source=hashnode&utm_medium=feed)

[Daniel Westgaard](https://hashnode.com/@danielw) · [May 31](https://hashnode.com/posts/repo-access-was-never-the-hard-part/6a1bf19820665204d4f927e0)

### [Repo access was never the hard part](https://riftmap.hashnode.dev/repo-access-was-never-the-hard-part?utm_source=hashnode&utm_medium=feed)

The multi-repo agent race is solving repository access. But access is plumbing — the cross-repo dependency graph is the part nobody upstream is parsing.

8 min read · [riftmap.hashnode.dev](https://riftmap.hashnode.dev/repo-access-was-never-the-hard-part?utm_source=hashnode&utm_medium=feed)
