They have a mechanism to stop the madness. Unless that repo has explicitly forbidden the use of any file.Ĭonsider other tools which have a similar design of searching parent directories like editorconfig.
If the outer repo has a root then there's really no way to safely submodule in another repo. NET project via a submodule into your repo. For the latter consider the act of including a. This can be done both by simple developer accident or by misunderstood design. If there is a stray file in their home directory then builds will suddenly, and quite silently, start changing.
Looking at a repo on Github is no longer enough to understand how a build works, have to consider every single directory structure the code is cloned into. Now the output, and possibly success or failure, of my build is dependent upon where on the machine a developer clones the repo. That seems like it is introducing unnecessary fragility into my build environment.
0 kommentar(er)
