Summary
Some platforms require \r\n line endings, but the current repository content or generated output may not preserve CRLF consistently.
Problem
When files or generated artifacts use \n only, certain platforms or tools may fail to parse them correctly, show formatting issues, or produce inconsistent behavior.
Expected
- Identify the files, generated outputs, or workflows that need CRLF line endings.
- Preserve
\r\n where platform compatibility requires it.
- Document the constraint if the behavior is intentional or platform-specific.
Acceptance Criteria
- The affected path is confirmed.
- The required content uses
\r\n on platforms that depend on CRLF.
- The repository behavior is documented or covered by a reproducible verification step.
Summary
Some platforms require
\r\nline endings, but the current repository content or generated output may not preserve CRLF consistently.Problem
When files or generated artifacts use
\nonly, certain platforms or tools may fail to parse them correctly, show formatting issues, or produce inconsistent behavior.Expected
\r\nwhere platform compatibility requires it.Acceptance Criteria
\r\non platforms that depend on CRLF.