🩹 [Patch]: Encode all PowerShell files using UTF8 with BOM#231
Merged
MariusStorhaug merged 1 commit intomainfrom Oct 12, 2025
Merged
🩹 [Patch]: Encode all PowerShell files using UTF8 with BOM#231MariusStorhaug merged 1 commit intomainfrom
MariusStorhaug merged 1 commit intomainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This pull request adds Unicode Byte Order Mark (BOM) encoding to PowerShell script files across the project to ensure proper encoding and compatibility, especially on Windows systems.
- Added UTF-8 BOM to all PowerShell script files
- No functional code changes made, only encoding updates
Reviewed Changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| tests/srcWithManifestTestRepo/tests/BeforeAll.ps1 | Added UTF-8 BOM to test setup script |
| tests/srcWithManifestTestRepo/tests/AfterAll.ps1 | Added UTF-8 BOM to test teardown script |
| tests/srcWithManifestTestRepo/src/variables/public/Planets.ps1 | Added UTF-8 BOM to planets variable definition |
| tests/srcTestRepo/tests/BeforeAll.ps1 | Added UTF-8 BOM to test setup script |
| tests/srcTestRepo/tests/AfterAll.ps1 | Added UTF-8 BOM to test teardown script |
| tests/srcTestRepo/src/variables/public/Planets.ps1 | Added UTF-8 BOM to planets variable definition |
| .specify/scripts/powershell/update-agent-context.ps1 | Added UTF-8 BOM to agent context update script |
| .specify/scripts/powershell/setup-plan.ps1 | Added UTF-8 BOM to plan setup script |
| .specify/scripts/powershell/create-new-feature.ps1 | Added UTF-8 BOM to feature creation script |
| .specify/scripts/powershell/common.ps1 | Added UTF-8 BOM to common functions script |
| .specify/scripts/powershell/check-prerequisites.ps1 | Added UTF-8 BOM to prerequisite checking script |
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.
Description
This pull request updates several PowerShell script files across the project. The main change is the addition of a Unicode Byte Order Mark (BOM) at the beginning of each file, which can help ensure proper encoding and compatibility, especially on Windows systems. No functional code changes have been made.