Honor BOM and CRLF for the isolated PowerShell launcher #53
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow up W-079 formatting conflict only. Completed launch behavior from PR196 remains accepted. dev-isolated.ps1 has UTF-8 BOM but LF, no effective eol attribute or editorconfig, and core.autocrlf=input. Apply a file-specific .gitattributes eol=crlf rule for scripts/dev-isolated.ps1 and materialize its worktree bytes as BOM plus CRLF without changing PowerShell content or any other ps1. Preserve existing attributes. Verify effective attribute and actual work-file encoding/endings, identical text after removing only CRLF encoding differences, and clean fork delivery. No new tests, launcher execution, rebuild, dependency install, new product behavior, operating Kandev changes, or upstream publication. Investigation and format readback belong to task fc32ebd6-8f69-43fd-8933-c7f703211f04.
W-080 done: added .gitattributes rule 'scripts/dev-isolated.ps1 text eol=crlf' (PR #198 merged c909b590d0); checkout verified UTF-8 BOM + 594 CRLF under core.autocrlf=input, PowerShell content unchanged.
W-080 cleanup: PR #198 merged into fork main (squash merge c909b590d0, branch deleted); shared checkout main == origin/main and already contains the merge; no blocked_by dependents to release; no remaining items; no follow-up proposals; no feature toggles shipped. Attained: .gitattributes rule 'scripts/dev-isolated.ps1 text eol=crlf', checkout UTF-8 BOM + 594 CRLF under core.autocrlf=input.