Jun 7
Fuck this Shit 🤯
Just got into a platform engineering rabbit hole on behalf of small-to-mid sized startup teams.
That are struggling with building and deploying their code while arguing about monorepo vs multirepo setups wasting time and money on build pipelines.
Will share.
1
1
66
assume multirepo, offer workspace config for a "project" instead of defaulting to folder = project. sdk and cli can do this; so can cursor 2; not sure how to do it in cursor 3
1
165
Apr 14
Idk, I’ve found, for example, monorepo style codebases to be far more amenable to agents than multirepo, and google is famously monorepo. A lot of practices that have are somewhat amenable to agents
1
197
Apr 10
great, we def need multirepo support, and also support for no repo at all tbh. We are using cursor automations together with slack and jira. Slack integration is great, jira integration not so good! tbf this is atlassian's fault
1
1
17
Apr 5
1 llm能力不够 monorepo不如multirepo好重构 因为纯vibe难免重构 平时改动也容易绕
2还有就是其实我vibe的都是些很简单的项目 没必要过早抽象 gpt反正老是有这个倾向
1
1
28
Apr 1
its better than the competition but i would only use it when multiagent, multirepo is a must
1
2
41
Mar 29
@cline please add support for multirepo tasks. Our product has microservices divided across multiple repositories so currently this is not useful for us.
1
1
216
Mar 18
Cria um diretório e faz clone em subditetorios, informa que é multirepo
1
139
Mar 17
Looks cool and informative. GitHub's is really lacking quick switches for multirepo/multirun workflows. And overall, GitHub has been lagging like hell recently 😅
1
1
97
Mar 9
Been using this for a while actually (before the AI hype / tool integrations)
Before I used to have ~4 clones of the main work repo and then I just found that working on different things was just annoying, cause when you run out of slots, you either clone a new one or checkout a different branch... but what if you have unpushed commits / stashes for that branch somewhere else? what if you wanna open a 5th? what if you don't want to run fetch 4 times rather just once, what if you wanna try a merge between multiple things that live in different repos, you need to coordinate pushing and pulling and then try locally
My main win for multirepo was having separate .env files, but we(claude) wrote a script that could you derive a .env from our root work repo, so when I say "make new worktree" it will make a worktree copy .env from the main one changing the db credentials to be a new DB and bootstrap everything, so now I have "however many repos I want" and cleaning them up is super easy
clone --depth 1 --local would probably be slightly slower and would also work, but wouldn't solve my issue with "branches/stashes are now isolated"
1
5
1,696
Feb 23
May you bring multirepo and aggregate to markdown? The main feature still kicks me asciidoctor
190
Built @panesagent to manage coding agents with native integration with codex app server, multirepo git, integrated terminal and native file editing :)
1
131
