Currently, getRepoOptions has logic to search up to the git root or even the filesystem root for a beachball config. This is really not necessary and could lead to unexpected behavior.
In v3, we should only look for a config at cliOptions.path (which is the project root or cwd). Potentially getCliOptions should also have a fallback to look for the package root if no project/git root is found.
Currently,
getRepoOptionshas logic to search up to the git root or even the filesystem root for a beachball config. This is really not necessary and could lead to unexpected behavior.In v3, we should only look for a config at
cliOptions.path(which is the project root or cwd). PotentiallygetCliOptionsshould also have a fallback to look for the package root if no project/git root is found.