You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/copilot-instructions.md
+19-1Lines changed: 19 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,28 @@ All source files in this repository use **UTF-8 with BOM** (`EF BB BF`).
4
4
5
5
When creating or editing files, always save them as UTF-8 with BOM. This applies to `.cs`, `.csproj`, `.yml`, `.md`, `.json`, and all other text files.
6
6
7
-
Do **not** save files as UTF-8 without BOM, ANSI, or Shift-JIS — doing so will corrupt Japanese content and break Visual Studio / MSBuild tooling.
7
+
**Exception — Linux tooling files: use UTF-8 without BOM.**
8
+
The following file types are processed by Linux tools (Docker, bash, VS Code Dev Containers) that do not tolerate a BOM and must be saved **without** BOM:
9
+
-`Dockerfile` and any file named `*.Dockerfile`
10
+
- Shell scripts (`.sh`)
11
+
-`devcontainer.json` and all files under `.devcontainer/`
12
+
13
+
Do **not** save files as UTF-8 without BOM, ANSI, or Shift-JIS — doing so will corrupt Japanese content and break Visual Studio / MSBuild tooling (for the files above that require BOM).
14
+
15
+
### Editing workflow requirement
16
+
17
+
Maintain correct encoding **during each edit/create step** — do not correct it in a follow-up step.
18
+
19
+
Do not rely on a final "bulk conversion/check" step at the end of the task.
20
+
21
+
**Important:** The `create_file` tool does **not** interpret `\uFEFF` in the content string as BOM bytes — it writes the literal six characters `\uFEFF`. Never place `\uFEFF` (or any Unicode escape for U+FEFF) directly in the `content` parameter. Instead, create the file first (BOM-free), then immediately apply the PowerShell conversion command below for files that require BOM.
8
22
9
23
### Verification
10
24
25
+
Do not run the verification/conversion commands on every edit by default.
26
+
Prevent encoding issues through edit/create operations that preserve UTF-8 BOM.
27
+
Run the commands below only when preservation cannot be guaranteed or when troubleshooting is required.
0 commit comments