3 ms·
Sorry, but as someone who has been in orgs that do both, mono repo is a mistake. Constant needs to pull unrelated changes before pushing, pipelines requiring t
by axaxs 8y ago
Sorry, but as someone who has been in orgs that do both, mono repo is a mistake. Constant needs to pull unrelated changes before pushing, pipelines requiring to grab the whole repo for dependencies, etc. I understand the arguments for mono repo, but never think it's nothing that outweighs the cons.
- robaato 8y agoWell those are issues around having a git mono repo - where the repo is the unit of change - you get it or you don't. With mono repos such as SVN or Perforce you just work on whatever subset you want.