Monorepo – Our Experience

Re:Monorepo – Our Experience by dmazzoni on Wednesday November 06, 2024 @04:30PM (#42069732)

> It's called a directory copy. Cut + paste. I'd add a tag with a comment pointing to the old repo (if needed). But probably after a few weeks, no one is going to look at the old repo.

Not in my experience. I use "git blame" all the time, and routinely read through commits from many years ago in order to understand why a particular method works the way it does.

Luckily, there are many tools for merging git repos into each other while preserving history. It's not as simple as copy and paste, but it's worth the extra efford.

[ Parent | on HN ]

Re:Monorepo – Our Experience by CRConrad on Friday November 08, 2024 @01:35PM (#42089299)

Any tips on where to find these tools, or just generally find out how that works?

[ Parent | on HN ]

Re:Monorepo – Our Experience by oftenwrong on Saturday November 09, 2024 @05:37AM (#42093667)

An approach I've used is to use https://github.com/newren/git-filter-repo (amazing, versatile tool) to put the tree into a subdirectory, and namespace its tags, and then merge that into another tree with --allow-unrelated-histories. I built a tool for an employer that automated this process for the purpose of consolidating an excessive number of repositories.

[ Parent | on HN ]

Re:Monorepo – Our Experience by CRConrad on Saturday November 09, 2024 @11:28AM (#42095240)

Thanks!

[ Parent | on HN ]