Standardize ASCII and .editorconfig line endings repo-wide; tighten doc conventions - #114
Conversation
- Setup: add the ruleset export/import procedure (delete classic protection, export/import the develop/main rulesets via gh api) and a signing-order warning to README; add matching agent instructions to AGENTS.md. - ASCII: replace em-dashes and other typographic Unicode (arrows, <=, ellipsis) across all docs with ASCII equivalents; add a Character Set rule to AGENTS.md (scientific symbols and developer-typed emoji are the only exceptions). - Line endings: bring all files into .editorconfig compliance (CRLF for the affected docs, workflows, dependabot.yml, devcontainer.json); add a Line Endings rule to AGENTS.md. - Tense: rewrite README in current-state form (drop now/no longer/restore framing); add a current-state rule to AGENTS.md.
There was a problem hiding this comment.
Pull request overview
This PR updates repository documentation and authoring conventions, with a focus on tightening prose/style rules (ASCII-by-default, current-state phrasing, setup/ruleset procedures) and normalizing line endings to match .editorconfig.
Changes:
- Expanded setup guidance in
README.md/AGENTS.md(ruleset export/import procedure and a stronger “sign from the first commit” warning). - Standardized documentation prose (ASCII substitutions, current-state phrasing) across multiple docs/style guides.
- Normalized line endings across docs/config files (including workflows and devcontainer JSON) to reduce editorconfig drift.
Reviewed changes
Copilot reviewed 8 out of 15 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds/updates setup + ruleset procedure documentation and rewrites prose for consistency. |
| PyPiLibrary/README.md | ASCII/prose normalization and formatting consistency for the Python-side README. |
| PyPiLibrary/CODESTYLE.md | ASCII/prose normalization for Python style guide. |
| HISTORY.md | Line-ending/format normalization (no substantive content change). |
| docs/ssh-signing.md | ASCII/prose normalization for signing documentation. |
| docs/host-setup.md | ASCII/prose normalization for host setup documentation. |
| docs/devcontainer.md | ASCII/prose normalization for devcontainer documentation. |
| CODESTYLE.md | ASCII/prose normalization for .NET style guide. |
| AGENTS.md | Adds “current-state”, “character set”, and “line endings” conventions and updates prose. |
| .github/workflows/test-pull-request.yml | Line-ending normalization only (per PR intent). |
| .github/workflows/publish-release.yml | Line-ending normalization only (per PR intent). |
| .github/dependabot.yml | Line-ending normalization only (per PR intent). |
| .github/copilot-instructions.md | Line-ending normalization only (but still contains non-ASCII symbols that now conflict with AGENTS.md rules). |
| .devcontainer/python/devcontainer.json | Line-ending normalization only (but contains typographic Unicode in comments). |
| .devcontainer/dotnet/devcontainer.json | Line-ending normalization only (but contains typographic Unicode in comments). |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Round-2 review fixes for PR #114: - Apply the ASCII convention to all tracked files, not just docs. An earlier sweep skipped .github/ (a buggy path filter) and non-.md files, leaving em-dashes/arrows in workflows, devcontainer.json, CodeGen *.cs, and the PyPI package. All converted - comments/docstrings/cosmetic strings only, EOL-preserving. - README + AGENTS: correct the signing warning. A re-sign rewrite changes every SHA and makes the rewriter the committer/signer; a rebase preserves the author field, so drop the 'authorship is lost' claim. - AGENTS: clarify the line-ending rule - new files follow .editorconfig, edits preserve existing endings, and normalizing a non-compliant file is a deliberate EOL-only change.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Round-3 review fixes for PR #114: - build-pypilibrary-task.yml: the ASCII sweep turned an em-dash at the start of a wrapped comment line into '# - ', which read as a bullet and broke the sentence. Rephrased so it reads as prose. - AGENTS Line Endings: relax 'never mixed into a content edit' - prefer an isolated EOL-only commit, but allow a repo-wide cleanup to normalize alongside content when called out and verified with --ignore-cr-at-eol.
Uh oh!
There was an error while loading. Please reload this page.
Round-4 review fix for PR #114: two App-token bullets said 'GitHub project security Settings'; the rest of the section (and GitHub's actual UI path) uses 'GitHub project Settings'. Made them consistent.
Uh oh!
There was an error while loading. Please reload this page.
Round-5 review fix for PR #114: an earlier edit that added the Line Endings subsection dropped the '### Quantitative Claims' heading, leaving its guidance as a stray bullet. Heading restored.
Uh oh!
There was an error while loading. Please reload this page.
Release of develop -> main. Two changes: - **Standardize ASCII and `.editorconfig` line endings repo-wide; tighten doc conventions (#114)** - replace typographic Unicode (em-dashes, arrows, `<=`, ellipsis) with ASCII across all tracked files; bring every file to its `.editorconfig` line ending; add the ruleset export/import + signing-order setup docs; add AGENTS rules (Character Set, Line Endings, current-state tense, ruleset-setup). Source edits are comments/docstrings/cosmetic-strings and line endings only - no logic change. - **Update codegen files (#113).** Merge-commit (not squash) per the branching model. The insertions/deletions count is dominated by line-ending normalization (whole-file churn under `* -text`); `git diff --ignore-cr-at-eol main...develop` isolates the real content edits.
Repository-wide text hygiene plus authoring-rule documentation. No logic changes - source edits are in comments/docstrings/cosmetic strings and line endings only.
What
<=, ellipsis, curly quotes) with ASCII across all tracked text files - docs, workflows,devcontainer.json,CodeGen/*.cs, and the PyPI package (comments/docstrings/cosmetic strings only). New AGENTS "Character Set" rule; scientific symbols and developer-typed emoji are the only exceptions..editorconfigline endings. Bring every file into compliance (CRLF for.md/.cs/XML/YAML/JSON/Windows-scripts, LF for.sh); several files had drifted to LF. New AGENTS "Line Endings" rule.develop/mainrulesets viagh api) and a signing-order warning.Scope note
This started as a docs-only pass. Copilot's review correctly flagged that the new ASCII rule was only half-applied - an earlier sweep had a bug that skipped
.github/and non-.mdfiles. I extended it to the whole repo so the rule and the tree are consistent. All source changes are non-functional (EOL-preserving; the PyPI smoke build re-validates thePyPiLibraryedits).Reviewing the diff
Line-ending normalization shows as whole-file churn under
* -text;git diff --ignore-cr-at-eolisolates the real content edits (small - mostly—->-in comments).