Skip to content

🐞 .gitattributes vs. content inconsistency #510

@kiniry

Description

@kiniry

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The electionguard-core2 repo's .gitattributes specifies eol=lf but the files were committed with CRLF. Thus, clones will be immediately dirty.

To remedy, make the specification agree with the contents. I propose that the right answer is to follow standard line ending conventions used the world-over for technical artifacts, which would mean fixing the files in the repository that were updated by someone on Windows that did not understand these kinds of things.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

- OS:

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions