Files
Craftimizer/.gitattributes
T
JonKazama-Hellion 356da24feb
Security / scan (push) Successful in 17s
Build / Build (Release) (push) Successful in 28s
Release / Build and attach release ZIP (push) Failing after 29s
Extend .gitattributes: source files to eol=lf
csharpier check fails with 'different line endings than formatting would
result in' when .cs files are CRLF. Linux dev box and Gitea Actions
runners both work with LF natively. Extend the LF-override to .cs,
.csproj, .sln, .yml, .yaml, .json, .md.

Asriel's original CRLF default still applies to file types not listed,
to keep the diff against upstream minimal.
2026-05-26 20:25:32 +02:00

26 lines
970 B
Plaintext

# Asriel's upstream default: CRLF for text files (Windows-only dev workflow).
# Kept intact to minimise the diff against upstream Craftimizer.
* text eol=crlf
# Hellion Forge override: shell scripts and git hooks MUST be LF only,
# otherwise bash on Linux refuses to execute them with
# "env: »bash\r«: Datei nicht gefunden". This blocked the v0.1.0 release
# pipeline push on Linux before .gitattributes was extended.
*.sh text eol=lf
.githooks/* text eol=lf
scripts/* text eol=lf
# csharpier check fails with "different line endings than formatting would
# result in" when .cs files are CRLF. The Gitea Actions runners are Linux
# and the local dev box is Linux too, so force LF for the entire source
# tree and the supporting text manifests.
*.cs text eol=lf
*.csproj text eol=lf
*.sln text eol=lf
*.yml text eol=lf
*.yaml text eol=lf
*.json text eol=lf
*.md text eol=lf
*.png binary