Skip to content

Treat dirty repos because of weird EOLs as a user error #6364

Description

@dkurepa

Every now and then, codeflows fail in weird ways because the service has a file that's always "dirty" and can't be staged because of a mix of EOLs.

When this happens, we should fail with a user error to notify repo owners to fix this file

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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