chore: normalize PowerShell files to UTF-8 BOM + CRLF and add .gitattributes - #5
Merged
Merged
Conversation
…ributes Align SPSDBMove with the SPS* repositories encoding policy: PowerShell files (.ps1) are stored as UTF-8 with BOM and checked out with CRLF; YAML, Markdown and JSON use LF without BOM. Windows PowerShell 5.1 reads BOM-less files as ANSI (the system code page), which corrupts non-ASCII characters; the BOM makes the encoding explicit and safe on SharePoint servers. Encoding-only change: file contents are otherwise unchanged.
Pester Test Results17 tests 17 ✅ 4s ⏱️ Results for commit 66805db. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Align SPSDBMove with the SPS* repositories encoding policy:
.ps1) stored as UTF-8 with BOM, checked out with CRLF..gitattributesreusing the shared SPS* template.Why
Windows PowerShell 5.1 reads BOM-less files as ANSI (the system code page), which corrupts non-ASCII characters. The BOM makes the encoding explicit and safe on SharePoint servers.
Scope
Encoding-only change — file contents are otherwise unchanged. The only per-file diff is the BOM on line 1 and the LF→CRLF line endings. No code logic, no config migration, no workflow changes.
Files re-encoded:
scripts/SPSDBMove.ps1tests/SPSDBMove.Tests.ps1Validation
Invoke-Pester -Path ./tests)../scripts.