We have 4 interal-only projects that all kind-of depend on each other and are all rolled out at the same time: backend, frontend and two shell wrappers for the

We have 4 interal-only projects that all kind-of depend on each other and are all rolled out at the same time: backend, frontend and two shell wrappers for the frontend (electron for windows, cordova for ipad) The total code base is still small enough for network/file system to not care (~10 devs working 10 years.) Since we're on Azure Devops, we currently have to create a pull requests for every project. If you change the naming of an API variable, you'll have to create two pull requests. You'll have to review those individually. The automatically triggered test runs will fail against the respective "old" version of each other and create noise. If, instead, we'd have a structure like this, the changes could be together: /src - backend (C#) - frontend (TypeScript) - ... Note that we're not planning to have a "shared" library or "common" editorconfig files, or changing _anything_ about code internals. Just tracking the folders in git together.