Skip to content

Should fail when an unexpected config section #163

Description

@kolayne

Currently, if there's an unexpected section in the codeowners.toml file, it is silently ignored. Presumably, this would only happen by mistake, in which case an explicit error would make it much easier to debug.

(I haven't tested whether the same happens when an unexpected option is present in an expected section, but I'd expect it to fail, too)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions