Skip to content

Coerce copilot to avoid emdash everywhere #52978

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
adegeo wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −0
Open

Coerce copilot to avoid emdash everywhere #52978

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .github/agents/docseditor.agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -230,6 +230,9 @@ When editing, focus on these areas in order of priority:
- ALWAYS use one space after periods, colons, question marks
- ALWAYS use no spaces around dashes: "Use pipelines—logical groups—to consolidate"
- ALWAYS add blank lines around markdown elements (don't add extra if they exist)
- TRY to avoid emdash and the various alternative dash characters; try to use other punctuation or formatting to achieve the same effect. Choose words over characters when possible
- OK to use compound adjectives with hyphens
- OK to use emdash mid-sentence for a clause or example; use sparingly
Comment on lines 231 to +235
Copy link

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new guidance on em dashes conflicts with the existing mandatory rule immediately above it. You currently say to "ALWAYS use no spaces around dashes" (with an em dash example), then "TRY to avoid" em dashes, then "OK to use" em dashes. Please consolidate/reword so the rules are consistent (for example: avoid em dashes where possible; if you must use an em dash, don’t include spaces around it; hyphens in compound modifiers are fine). Also consider naming the specific dash characters (em dash vs en dash) so the instruction is unambiguous.

Suggested change
- ALWAYS use no spaces around dashes: "Use pipelines—logical groups—to consolidate"
- ALWAYS add blank lines around markdown elements (don't add extra if they exist)
- TRY to avoid emdash and the various alternative dash characters; try to use other punctuation or formatting to achieve the same effect. Choose words over characters when possible
- OK to use compound adjectives with hyphens
- OK to use emdash mid-sentence for a clause or example; use sparingly
- ALWAYS add blank lines around markdown elements (don't add extra if they exist)
- TRY to avoid em dashes (—) where possible; prefer other punctuation, formatting, or clearer wording
- If you must use an em dash (—), use no spaces around it: "Use pipelines—logical groups—to consolidate"
- OK to use hyphens (-) in compound adjectives

Copilot uses AI. Check for mistakes.
Comment on lines +233 to +235
Copy link

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"emdash" should be written as "em dash" (and it may help to include the glyph "—" the first time for clarity).

Suggested change
- TRY to avoid emdash and the various alternative dash characters; try to use other punctuation or formatting to achieve the same effect. Choose words over characters when possible
- OK to use compound adjectives with hyphens
- OK to use emdash mid-sentence for a clause or example; use sparingly
- TRY to avoid em dash and the various alternative dash characters; try to use other punctuation or formatting to achieve the same effect. Choose words over characters when possible
- OK to use compound adjectives with hyphens
- OK to use an em dash (—) mid-sentence for a clause or example; use sparingly

Copilot uses AI. Check for mistakes.

## API REFERENCES

Expand Down
Loading