New answers tagged

-1 votes

monorepo - Single monorepo for multiple large-scale, company-sized projects

Things that change together should go together. Let us remove any confusion or uncertainties: files published on any path are uniquely qualified, whether you have a monorepo or dozens of them--the ...
Filip Dupanović's user avatar
0 votes

Suggestion a Safe Strategy to Migrate to Monorepo

I've done something similar in the past, when Yarn came out, and there wasn't yet practical support for monorepos or private registries, in a situation where there was a main monolith application, ...
Filip Dupanović's user avatar
1 vote

Does squashing pull requests break git's merging algorithm?

TL;DR: after the squash merge, you should merge main into feature1, then feature1 into feature2, to establish the common ancestors to avoid conflicts. These squash merge policies exist to make sure ...
Calmarius's user avatar
  • 1,903
-2 votes

How to handle nested submodule dependencies

You've not specified the langauge, but if the submodules are reasonably slow to change and can be versioned separately, then it may make sense to compile them and ship packages.
pjc50's user avatar
  • 13.3k

Top 50 recent answers are included