Skip to content

Don't search up for the config #1175

Description

@ecraig12345

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or requestv3

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions