Whoa, that's tough. Sounds like you have indeed hit a case where > the tool makes far more sense in the context of Google’s systems and architecture Bazel sho

Whoa, that's tough. Sounds like you have indeed hit a case where > the tool makes far more sense in the context of Google’s systems and architecture Bazel should not behave like what you described (at least in my experience) for in-repo sources and build rules. Except that the world does not work in this way, so they added a duct tape called "using workspace rules to fetch and potentially build external dependencies", which is as fragile as a ./build.sh pulling in all your dependencies. And Google? They did vendor everything they use at //third_party in their monorepo, so (╯‵□′)╯︵┻━┻