As software development teams grow in size and complexity, the decision of whether to use a monorepo or a multi repo architecture becomes increasin...
For further actions, you may consider blocking this person and/or reporting abuse
Just some remarks:
Can be mitigated to have a separate shared-code repository. This can be a submodule of other project repos or it can create a library that can be consumed by other repos.
Can be mitigated to have build pipelines focus on changes from specific directories. Although may be more complex.
I have used a monorepo before and for new projects we started to use multi repo. I'm not sure if I'd do that switch again... Most of the times people work on multiple projects and have to checkout and update all individual repos separately... We use scripts to do that now, and we have a "master" repo of which all other project repos are submodules. Still I feel it's harder to maintain this way...