Skip to content

Support copilot: fix email subject mojibake + role-add completion tense#3596

Merged
bernardhanna merged 1 commit into
devfrom
fix/support-email-subject-and-tense
Jun 30, 2026
Merged

Support copilot: fix email subject mojibake + role-add completion tense#3596
bernardhanna merged 1 commit into
devfrom
fix/support-email-subject-and-tense

Conversation

@bernardhanna

Copy link
Copy Markdown
Collaborator

Summary

  • Subject mojibake: the outgoing Subject: header was emitted as raw UTF-8, so characters like the em-dash and accented names showed as —. It's now RFC 2047 MIME-encoded (only when it contains non-ASCII), via mb_encode_mimeheader with a base64 fallback.
  • Completion tense: the role-add completion email mapped the executed added status to "will be added". It now reads "role added" for accounts actually changed; the dry-run still reads "will be added" (would_add).

Test plan

  • SupportCompletionEmailCopyTest::test_completion_body_for_role_add_uses_past_tense_per_account
  • existing dry-run / completion / resolver / role-add suites (16 pass)

Made with Cursor

…ense

- MIME-encode (RFC 2047) the outgoing Subject header so non-ASCII characters
  (em-dash, accents in names) are no longer mangled into "—".
- Completion email now reads "role added" for accounts actually changed,
  instead of "will be added"; dry-run still reads "will be added".

Co-authored-by: Cursor <cursoragent@cursor.com>
@bernardhanna bernardhanna merged commit a3ac808 into dev Jun 30, 2026
@bernardhanna bernardhanna deleted the fix/support-email-subject-and-tense branch June 30, 2026 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant