The .editorconfig defaults block (an always-verbatim carry) labels the JSON section:
# Json and JsonC files
[*.{json,jsonc}]CODESTYLE.md -> General -> "Tooling Names and Casing" requires each tool/format's official casing in docs and prose. The official casing is JSON / JSONC, so the comment should read # JSON and JSONC files.
Because the block is carried verbatim, every derived repo inherits the lowercase casing, and a Copilot reviewer flags it against the casing rule on each re-sync. Fixing it in the template propagates the correct casing to all downstreams.
Found while re-syncing a downstream.
The
.editorconfigdefaults block (an always-verbatim carry) labels the JSON section:CODESTYLE.md-> General -> "Tooling Names and Casing" requires each tool/format's official casing in docs and prose. The official casing is JSON / JSONC, so the comment should read# JSON and JSONC files.Because the block is carried verbatim, every derived repo inherits the lowercase casing, and a Copilot reviewer flags it against the casing rule on each re-sync. Fixing it in the template propagates the correct casing to all downstreams.
Found while re-syncing a downstream.